From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Shay Rojansky <roji(at)roji(dot)org>, Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Cached/global query plans, autopreparation |
Date: | 2018-03-02 20:51:46 |
Message-ID: | 23312.1520023906@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2018-03-02 15:29:09 -0500, Bruce Momjian wrote:
>> While I have heard people complain about how other databases cache
>> prepare plans, I have heard few complaints about the Postgres approach,
>> and I haven't even heard of people asking to control the documented "five
>> or more" behavior.
> This *constantly* is a problem.
Yeah, I've certainly heard complaints about it. I do agree with
Bruce's conclusion that we should try to improve that behavior;
but it's not entirely clear how. (A user-frobbable knob isn't
necessarily the best answer.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2018-03-02 21:06:32 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |
Previous Message | David Steele | 2018-03-02 20:41:57 | Re: [HACKERS] Creating backup history files for backups taken from standbys |