| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | James Coleman <jtc331(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Discarding DISCARD ALL |
| Date: | 2021-01-20 14:58:39 |
| Message-ID: | CANP8+jJC+4zTLCsngU3=XzAg+W=Md55Rqepvv+ZMDQ5sZfwfvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 20 Jan 2021 at 14:21, James Coleman <jtc331(at)gmail(dot)com> wrote:
> An alternative approach that occurred to me while typing this reply: a
> setting in Postgres that would disallow setting session level GUCs
> (i.e., enforce `SET LOCAL` transaction level usage instead) would
> remove a large chunk of our need to set server_reset_query_always=1
> (and more interestingly it'd highlight when broken code gets pushed).
> But even with that, I see some value in the proposed setting since
> there is additional session state beyond GUCs.
With transaction_cleanup=on we could force all SETs to be SET LOCAL.
The point is that if we declare ahead of time that the transaction
will be reset then we can act differently and more easily for various
circumstances, for SETs, for Temp tables and others.
--
Simon Riggs http://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dian M Fay | 2021-01-20 14:58:43 | Re: [HACKERS] [PATCH] Generic type subscripting |
| Previous Message | James Coleman | 2021-01-20 14:20:51 | Re: Discarding DISCARD ALL |