From: | Matteo Beccati <php(at)beccati(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Postgres Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: DISCARD ALL failing to acquire locks on pg_listen |
Date: | 2009-02-11 16:47:48 |
Message-ID: | 49930134.4020609@beccati.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Tom,
>> Given I was using 8.3, it seemed quite right to set the reset statement
>> to "ABORT; DISCARD ALL". Everything works fine, until a load spike
>> happens and pgpool-II reset queries start to lag behind, with DISCARD
>> ALL failing to acquire an exclusive locks on the pg_listen system table,
>> although the application isn't using any LISTEN/NOTIFY. The reason was
>> not obvious to me, but looking at the man page explained a lot: DISCARD
>> ALL also performs an "UNLISTEN *".
>
> Seems like we could/should fix UNLISTEN * to not do anything if it is
> known that the current backend never did any LISTENs.
Ok, I'll take sometime tonight to give my patch a try and eventually
submit it.
Cheers
--
Matteo Beccati
OpenX - http://www.openx.org
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2009-02-11 16:50:32 | Re: Optimization rules for semi and anti joins |
Previous Message | Jonah H. Harris | 2009-02-11 16:44:33 | Re: Optimization rules for semi and anti joins |