Postgres Pro
Downloads
Home   >   mailing lists

Re: Default setting for enable_hashagg_disk - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Default setting for enable_hashagg_disk
Date
Msg-id 2210835.1594477622@sss.pgh.pa.us
Whole thread Raw
In response to Re: Default setting for enable_hashagg_disk  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Default setting for enable_hashagg_disk  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
Tree view 
David Rowley <dgrowleyml@gmail.com> writes:
> hmm yeah. It's unfortunate, but I'm not sure how I'd have implemented
> it differently.  The problem is made worse by the fact that we'll only
> release the memory for the hash table during ExecEndHashJoin(). If the
> planner had some ability to provide the executor with knowledge that
> the node would never be rescanned, then the executor could release the
> memory for the hash table after the join is complete.

EXEC_FLAG_REWIND seems to fit the bill already?

            regards, tom lane

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Default setting for enable_hashagg_disk
Next
From: Tom Lane
Date:
Subject: Re: min_safe_lsn column in pg_replication_slots view