On Wed, Nov 26, 2008 at 8:13 PM, Gregory Stark <[EMAIL PROTECTED]> 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 http://www.postgresql.org/docs/8.3/interactive/sql-discard.html . 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. -- Guillaume -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
