Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Size limit when using postgis data source #16342

Open
qgib opened this issue Mar 16, 2013 · 7 comments
Open

Size limit when using postgis data source #16342

qgib opened this issue Mar 16, 2013 · 7 comments
Labels
Feature Request Processing Relating to QGIS Processing framework or individual Processing algorithms

Comments

@qgib
Copy link
Contributor

qgib commented Mar 16, 2013 •
edited

Author Name: Alex Mandel (Alex Mandel)
Original Redmine Issue: 7369

Redmine category:processing/saga
Assignee: Victor Olaya

My layer that I want to run IDW on in postgis is 3.6G. Sextante trying to write this out to a temp shapefile on the system before passing to SAGA is a huge problem that will never work because the dbf table exceeds the 2 G limit. I let it run for 8 hours and if never seems to finish even making the shp. So this may be a SAGA bug for requiring shp input but we need to find a way to allow passing large data to analysis algorithms with a memory provider or using postgis directly. I have 32 G of RAM and am on 64 bit Ubuntu.

Related issue(s): #17058 (relates)
Redmine related issue(s): 8249
@qgib
Copy link
Contributor Author

qgib commented Mar 16, 2013

Author Name: Victor Olaya (@volaya)

I am afraid there is nothing we can do for that. SAGA supports those formats, and it is a limitation of the software. The only solution is to develope new things in saga...

  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Mar 18, 2013

Author Name: Alex Mandel (Alex Mandel)

Victor Olaya wrote:

I am afraid there is nothing we can do for that. SAGA supports those formats, and it is a limitation of the software. The only solution is to develope new things in saga...

What about warning users that an operation may not finish, or that it failed because the layer is too big for shp. Mine just sat locked up all night.

@qgib
Copy link
Contributor Author

qgib commented Jun 21, 2014

Author Name: Giovanni Manghi (@gioman)

  • status_id was changed from Feedback to Open

@qgib
Copy link
Contributor Author

qgib commented Oct 4, 2014

Author Name: Giovanni Manghi (@gioman)

  • project_id was changed from 78 to 17
  • category_id removed 56
  • crashes_corrupts_data was configured as 0
  • version was configured as 2.4.0

@qgib
Copy link
Contributor Author

qgib commented Oct 4, 2014

Author Name: Giovanni Manghi (@gioman)

  • category_id was configured as Processing/SAGA

@qgib
Copy link
Contributor Author

qgib commented Jun 1, 2015

Author Name: Giovanni Manghi (@gioman)

  • tracker_id was changed from 1 to 2

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)

  • easy_fix was configured as 0

@qgib qgib added Feature Request Processing Relating to QGIS Processing framework or individual Processing algorithms labels May 24, 2019
@qgib qgib mentioned this issue May 25, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature Request Processing Relating to QGIS Processing framework or individual Processing algorithms
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@qgib