Re: [bugfix] DISCARD ALL does not release advisory locks

From: "Robert Haas" <robertmhaas(at)gmail(dot)com>
To: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
Cc: "Marko Kreen" <markokr(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Postgres Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [bugfix] DISCARD ALL does not release advisory locks
Date: 2008-11-26 19:11:57
Message-ID: 603c8f070811261111x756a5ab6iaf372e07c6836d19@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I see your point but there's a pretty high standard for changing
> existing behavior in bugfix releases. It's just as likely to introduce
> an application bug as to fix one...suppose the application is using
> both 'discard all' for prepared statements and advisory locks for
> other purposes. You could break that application.

I would expect someone to use "DEALLOCATE ALL" for that purpose, but
it is true that people don't always do what you expect...

...Robert

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2008-11-26 19:13:33 Re: [bugfix] DISCARD ALL does not release advisory locks
Previous Message Gregory Stark 2008-11-26 19:08:25 Re: Enhancement to pg_dump