Timeline for Query in QGIS is significantly slower, than in pgAdmin
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 28, 2019 at 10:03 | comment | added | DIV | Thanks, I will check that out. | |
| Aug 26, 2019 at 9:26 | comment | added | Joseph | @DIV - In terms of logging information, you could take a look at this post: Enable LOG Messages in QGIS | |
| Aug 23, 2019 at 15:28 | comment | added | Joseph | @DIV - Good question, certainly worth asking the community :) | |
| Aug 23, 2019 at 15:04 | comment | added | DIV | Do you know if there is a way to see what QGIS is doing (like logs, but more detailed)? With that information I would be able to at least compare, what makes QGIS so slow, which specific part of the code or a function, etc. | |
| Aug 23, 2019 at 14:29 | comment | added | DIV | Tables are joined by pure SQL. Nothing was done via the interface. Ok, thanks Joseph, I'll try that out and see what result gonna get. Looks promising. | |
| Aug 23, 2019 at 13:32 | comment | added | Joseph |
@DIV - How did you join the tables, via the interface or script? QGIS can set up a memory cache when joining. You could consider running the Execute SQL tool from the Processing Toolbox which I would assume could run a query as fast as PostgreSQL.
|
|
| Aug 23, 2019 at 13:19 | comment | added | DIV | Yeah, I surmised that you forgot to mention that removing part, but I still think it would perform much like that layer without join, so. If you talking about something more than QGIS build-in cache system, then no. Do I have to set it up by myself with third party libraries or QGIS can help me with that with some more advanced settings? | |
| Aug 23, 2019 at 9:36 | comment | added | Joseph | @DIV - Were you using memory cache when the join was made? I forgot to mention that the point of using a virtual field to copy the values would be that you could remove the join straight after. So first you join the table, create a virtual field and copy values over, remove the join and then run the query. | |
| Aug 22, 2019 at 13:25 | comment | added | DIV | I see your point, but I don't think it will tell as much more, than what I've done already. I have ca. 30 attribute columns and only 3 joined ones. As I said, if I get rid of joined fields everything works fine. Normal field or virtual, as far as there's no join, it doesn't matter, it will be fast anyway. Please elaborate, if I'm wrong. | |
| Aug 22, 2019 at 13:07 | comment | added | Joseph | @DIV - Could you create a virtual field in your main layer and copy the values from the joined field? Then run the query on the new virtual field and see if this makes any difference? | |
| Aug 22, 2019 at 13:04 | comment | added | DIV | I've tried that already, and there was no much difference. I'm starting to believe tbh, that query on table with joined data is just too much for QGIS. Without joined data works as fast as pgAdmin. And yes, there was a type. Fixed. | |
| Aug 22, 2019 at 12:53 | history | answered | Joseph | CC BY-SA 4.0 |