Jeff Janes wrote:
I think what I would do next is EXPLAIN (without ANALYZE) one of the
queries repeatedly, say once a second, while the other query either
runs or doesn't run repeatedly, that is the other query runs for 11
minutes (or however it takes to run), and then sleeps for 11 minutes
i
On 30.11.2013 00:48, Tom Lane wrote:
Are you explicitly ANALYZE'ing the newly-built tables in your script,
or are you just trusting auto-analyze to get the job done?
Hi Tom,
there is an explicit analyze of the table being done between filling the
table with values and running this query. I sket
Hi Jeff,
thanks for the answer.
On 29.11.2013 23:42, Jeff Janes wrote:
The planner is not aware of what else is going on in the server
I was not aware of this as well.
I'd guess that the 2nd database is missing the geometry index, or has
it defined in some different way such that the database
Dear all,
I have a quite strange problem running an extensive query on geo data
checking for crossing ways. I don't know if this is a postgres or postgis
problem, but I hope you can help. Running one thread is no problem, it
finishes within 10-15 minutes. Run two of those queries in parallel and
t
