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.

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

Crash When Using Relationships with Large PostGIS Tables #18025

Closed
qgib opened this issue Jan 26, 2014 · 4 comments
Closed

Crash When Using Relationships with Large PostGIS Tables #18025

qgib opened this issue Jan 26, 2014 · 4 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption High Priority Vectors Related to general vector layer handling (not specific data formats)

Comments

@qgib
Copy link
Contributor

qgib commented Jan 26, 2014

Author Name: Jeremy Palmer (@palmerj)
Original Redmine Issue: 9431
Affected QGIS version: master
Redmine category:vectors


Does this feature support large relationship tables from a database? I tried to build a relationship between PostgreSQL tables where the related table has about 2 million rows (which has foreign key column indexed). However when I tried to do a feature info on the map canvas QGIS hung for 20mins and then crashed. Does it try to fetch and cache all of the relationship data upfront, rather than do a database index look-up each time?

Note relationship fields are defined as int4 in PostgreSQL.

@qgib
Copy link
Contributor Author

qgib commented Jan 26, 2014

Author Name: Andreas Neumann (@andreasneumann)


Jeremy - I am not the developer of this feature. But yes - currently, the tables are all fetched to the client and then the relationship is built on the client. This is necessary because QGIS supports also file-based data sources.

However, Matthias, the author of this feature plans to do a QGIS expression to database-expression compiler that should be able to do the filtering in the database. You will have to be patient and wait a bit though. It won't be released with QGIS 2.2.

@qgib
Copy link
Contributor Author

qgib commented Jan 27, 2014

Author Name: Giovanni Manghi (@gioman)


  • os_version was changed from 12.04 to
  • crashes_corrupts_data was changed from 0 to 1
  • operating_system was changed from Ubuntu to
  • priority_id was changed from Normal to High

@qgib
Copy link
Contributor Author

qgib commented Jan 28, 2014

Author Name: Matthias Kuhn (@m-kuhn)


Hi Jeremy,

It would be very helpful if you could attach a stacktrace of your crash and check how the memory consumption behaves before the crash, so we could try to figure out, where exactly the problem is.

It indeed does not (yet) make use of indexes, and instead iterates over all the features and filters them locally. I plan to integrate such a functionality in future releases and will be looking for funding for this (probably starting around May). If you are considering to help funding such a development, please contact me via email.

PS: I assume it affects master (this feature was not included in 2.0.1).


  • status_id was changed from Open to Feedback
  • version was changed from 2.0.1 to master

@qgib
Copy link
Contributor Author

qgib commented Jul 28, 2014

Author Name: Matthias Kuhn (@m-kuhn)


Closed due to lack of feedback.
If this is still an issue, please provide the necessary information and reopen.


  • status_id was changed from Feedback to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Vectors Related to general vector layer handling (not specific data formats) Crash/Data Corruption labels May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption High Priority Vectors Related to general vector layer handling (not specific data formats)
Projects
None yet
Development

No branches or pull requests

1 participant