Postgres Pro
Downloads
Home   >   mailing lists

Re: Should work_mem be stable for a prepared statement? - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Should work_mem be stable for a prepared statement?
Date
Msg-id CAKAnmmJDsTx967Mb_2de028NCwqRGuG9OVy19sd1nWTp01fM6Q@mail.gmail.com
Whole thread Raw
In response to Should work_mem be stable for a prepared statement?  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
Tree view
On Thu, Feb 27, 2025 at 1:42 PM Jeff Davis <pgsql@j-davis.com> wrote:
It would make more sense to me if we either (a) enforced work_mem as it was at the time of planning; or (b) replanned if executed with a different work_mem (similar to how we replan sometimes with different parameters).

Definitely (b). 

But I'm not sure whether someone might be relying on the existing behavior?

I cannot fathom a reason why.

Cheers,
Greg

--
Enterprise Postgres Software Products & Tech Support

pgsql-hackers by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Update docs for UUID data type
Next
From: Robert Haas
Date:
Subject: Re: [PROPOSAL] : Disallow use of empty column name in (column_name '') in ALTER or CREATE of foreign table.