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

From Sami Imseih
Subject Re: Should work_mem be stable for a prepared statement?
Date
Msg-id CAA5RZ0vCnPZseUD4moLEDZkhYaUf9PDwY6fxLGtq=hEEsEEryA@mail.gmail.com
Whole thread Raw
In response to Re: Should work_mem be stable for a prepared statement?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Should work_mem be stable for a prepared statement?
List pgsql-hackers
> The argument for treating work_mem specially is that it has effects at
> both plan time and run time, so that the planner's cost assumptions
> are invalidated if the executor uses a different value than the
> planner did.

I see that now. Thanks!

> Maybe that refactoring is one that would conveniently apply to
> other GUCs, or maybe it isn't.  I'm content to await details
> before arguing about what we "should" do.

Agree.

--
Sami



pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Log connection establishment timings
Next
From: Jeff Davis
Date:
Subject: Re: [18] CREATE SUBSCRIPTION ... SERVER