Re: DISCARD ALL (Again)

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.