Hi,
there are many Hash and Merge joins that may generate a lot of temp space,
it could also be a problem of forgotten column in the join.
Could you also provide indexes definitions (pk, uk and others)
with the EXPLAIN (ANALYZE BUFFERS)
(you can limit the scope of the query to help it to finish
Hello,
I have one question… Why you using so huge amount of grouping columns? Is there
some reason for it? It is not definitelly fast method. I would prefer firstly
do named query grouped by ids (account_id, candidate_id, parent_id) and then
left join table candidates (to get rest of requested
Cory Tucker wrote:
> I have a query that is using a tremendous amount of temp disk space given the
> overall size of the dataset.
> I'd love for someone to try to explain what PG is doing and why its using so
> much space for the query.
It could be a sort or a hash operation.
Do determine what
