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

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

"Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:
> On Mon, Nov 24, 2008 at 10:25 AM, Marko Kreen <markokr(at)gmail(dot)com> wrote:
>> IOW, DISCARD ALL should be functionally equivalent to backend exit.

> Having done a lot of work with advisory locks, I support this change.
> Advisory locks are essentially session scoped objects like prepared
> statements or notifies. It's only natural to clean them up in the
> same way.

> That said, I don't think this should be backpatched to 8.3.

Done but not back-patched.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-26 01:33:23 Re: Simple postgresql.conf wizard
Previous Message Dann Corbit 2008-11-26 01:18:59 Re: Simple postgresql.conf wizard