On Wed, Nov 26, 2008 at 8:13 PM, Gregory Stark <stark(at)enterprisedb(dot)com> wrote:
> DISCARD ALL was specifically added in 8.3 for the purpose of connection
> poolers to be a "big hammer" that exactly emulates a new session. I'm somewhat
> skeptical that there are any applications using it directly at all, and doubly
> so that they would be using it and expecting advisory locks to persist.
> I think the second and third points are pretty convincing.
I kinda agree with you. The only problem IMHO is that we described in
the doc exactly what it does and not simply as the big hammer it was
supposed to be. See
You can't guarantee that nobody checked the doc to see if it discards
advisory locks even if it's highly unlikely.
That said, I'm more for the backpatching too.
In response to
pgsql-hackers by date
|Next:||From: Decibel!||Date: 2008-11-26 19:32:53|
|Subject: Re: Column reordering in pg_dump|
|Previous:||From: Decibel!||Date: 2008-11-26 19:25:56|
|Subject: Re: Simple postgresql.conf wizard|