Re: DISCARD ALL (Again) - Mailing list pgsql-hackers

From David G Johnston
Subject Re: DISCARD ALL (Again)
Date
Msg-id CAKFQuwZA+UdPTpd3WgKZVg2EJCP7OBbVUMK-9TGsaBW71Efn+g@mail.gmail.com
Whole thread Raw
In response to Re: DISCARD ALL (Again)  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: DISCARD ALL (Again)  (Stephen Frost <sfrost@snowman.net>)
Re: DISCARD ALL (Again)  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers

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.

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.

David J.




View this message in context: Re: DISCARD ALL (Again)
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Clock sweep not caching enough B-Tree leaf pages?
Next
From: Stephen Frost
Date:
Subject: Re: DISCARD ALL (Again)