Re: Cached/global query plans, autopreparation - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Cached/global query plans, autopreparation
Date
Msg-id 10279.1518643173@sss.pgh.pa.us
Whole thread Raw
In response to Re: Cached/global query plans, autopreparation  (Andres Freund <andres@anarazel.de>)
Responses Re: Cached/global query plans, autopreparation  ("henry@visionlink.org" <henry@visionlink.org>)
Re: Cached/global query plans, autopreparation  (Shay Rojansky <roji@roji.org>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2018-02-13 09:13:09 -0800, Shay Rojansky wrote:
>> Was wondering if anyone has a reaction to my email below about statement
>> preparation, was it too long? :)

> Well, the issue is that implementing this is a major piece of work. This
> post doesn't offer either resources nor a simpler way to do so. There's
> no huge debate about the benefit of having a global plan cache, so I'm
> not that surprised there's not a huge debate about a post arguing that
> we should have one.

Actually, I'm pretty darn skeptical about the value of such a cache for
most use-cases.  But as long as it can be turned off and doesn't leave
residual overhead nor massive added code cruft, I won't stand in the way
of someone else investing their time in it.

In any case, as you say, it's moot until somebody steps up to do it.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: tapeblocks is uninitialized in logtape.c
Next
From: Alvaro Herrera
Date:
Subject: Re: FOR EACH ROW triggers on partitioned tables