| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "fabriziomello(at)gmail(dot)com" <fabriziomello(at)gmail(dot)com> |
| Cc: | dmitriy(at)riabov(dot)info, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14877: DISCARD ALL incorrectly resets user parameters |
| Date: | 2017-10-27 14:05:44 |
| Message-ID: | CAKFQuwa2cKYtSvZkp0JiDeHAhf7yLzm230TbScixXc2KGCPUmA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 27, 2017 at 6:43 AM, Fabrízio de Royes Mello <
fabriziomello(at)gmail(dot)com> wrote:
>
> > Bug reference: 14877
> > Logged by: Dmitriy Riabov
> >
> Why do you think this wrong? This is the default behavior of DISCARD ALL
> since when 8.3 introduced it.
>
>
Docs say DISCARD ALL means:
SET SESSION AUTHORIZATION DEFAULT;
RESET ALL;
DEALLOCATE ALL;
CLOSE ALL;
UNLISTEN *;
SELECT pg_advisory_unlock_all();
DISCARD PLANS;
DISCARD SEQUENCES;
DISCARD TEMP;
The "RESET ALL" command is what causes the GUCs to be reset. If you don't
wish for them to be reset create a function the does all of the above minus
the RESET ALL.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabrízio de Royes Mello | 2017-10-27 14:22:15 | Re: BUG #14877: DISCARD ALL incorrectly resets user parameters |
| Previous Message | Fabrízio de Royes Mello | 2017-10-27 13:43:30 | Re: BUG #14877: DISCARD ALL incorrectly resets user parameters |