| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: DISCARD ALL (Again) |
| Date: | 2014-04-18 02:12:35 |
| Message-ID: | 53508A13.9070703@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04/17/2014 07:07 PM, David G Johnston wrote:
>
> On 04/17/2014 05:24 PM, Tom Lane wrote:
> > On the whole I'm not sure this is something we ought to get into.
> > If you really need a fresh session, maybe you should start a
> > fresh session.
>
>
> Isn't the whole point to avoid the reconnection overhead, especially for
> connection poolers? DISCARD ALL shouldn't cause any cleanup that
> wouldn't otherwise occur when a session disconnects. True global data
> (not just session global) should be excluded.
The GD is global to the session only (Like temp tables).
>
> A better wording of the promise would be: "discard all" leaves the
> session in the same state it would be in if the underlying connection
> were dropped and re-established.
Except that it doesn't.
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
Political Correctness is for cowards.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-04-18 02:15:15 | Re: DISCARD ALL (Again) |
| Previous Message | David G Johnston | 2014-04-18 02:07:55 | Re: DISCARD ALL (Again) |