Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan
Date
Msg-id CAFj8pRCfC5Wx1HCds3EnnBW_a_LrrvN_=phohjT6-pXewjMwQA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan
List pgsql-hackers
Tree view


2017-09-19 18:33 GMT+02:00 Robert Haas <robertmhaas@gmail.com>:
On Mon, Sep 18, 2017 at 11:46 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> There is possibility to introduce new compile option #option to disable plan
> cache on function scope. Do you think so it is acceptable solution? It is
> step forward.

You can already set a GUC with function scope.  I'm not getting your point.

yes, it is true. But implementation of #option is limited to PLpgSQL - so there is not any too much questions - GUC is global - there is lot of points:

* what is correct impact on PREPARE
* what is correct impact on EXECUTE
* what should be done if this GUC is changed ..

Regards

Pavel


--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] PG 10 release notes