Re: DISCARD ALL (Again)

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: DISCARD ALL (Again)
Date: 2014-04-18 02:15:15
Message-ID: 20140418021515.GT2556@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* David G Johnston (david(dot)g(dot)johnston(at)gmail(dot)com) 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.

Err, this is per-backend global data, so it will get cleaned up on
session disconnect.

> 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.

This is not accurate.

Thanks,

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Johnston 2014-04-18 02:18:03 Re: DISCARD ALL (Again)
Previous Message Joshua D. Drake 2014-04-18 02:12:35 Re: DISCARD ALL (Again)