| 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:26:39 |
| Message-ID: | CAKFQuwbQ40dUuNbQb8R9h53WD1LOV2dVEJv=LydJLwt+dxZQGw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 27, 2017 at 7:22 AM, Fabrízio de Royes Mello <
fabriziomello(at)gmail(dot)com> wrote:
> On Fri, Oct 27, 2017 at 12:05 PM, David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> I wonder if be nice to have some new DISCARD construct to cover different
> use cases, something like:
>
> DISCARD { ALL | PLANS | TEMP | SEQUENCES | ( { SESSION AUTHORIZARION |
> RESET | PREPARED STATEMENT | CURSORS | NOTIFY | ADVISORY LOCKS | PLANS |
> SEQUENCES | TEMP } [, ...] ) }
>
>
DISCARD ALL ( RESET false ) ...
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jordan Lewis | 2017-10-27 16:18:53 | ORDER BY $1 behaves inconsistently |
| Previous Message | Fabrízio de Royes Mello | 2017-10-27 14:22:15 | Re: BUG #14877: DISCARD ALL incorrectly resets user parameters |