Re: BUG #1184: listeners not cleaned on crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Radim Kolar" <hsn(at)netmag(dot)cz>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1184: listeners not cleaned on crash
Date: 2004-06-27 22:07:44
Message-ID: 14255.1088374064@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> writes:
> Description: listeners not cleaned on crash

This is a deficiency, without doubt, but it's always seemed like a
mighty low-priority one to me. There already is a provision for
deleting entries when they are found not to refer to any existing
process, so the odds of actually sending a mistaken notify seem low.

> This is a very annoying bug if you are running slony1 replication system.

If slony reacts badly to an extra notification then I think that's a
slony problem more than anything else. It shouldn't be that fragile.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kris Jurka 2004-06-27 23:07:43 PREPARE(d) statements and modifying columns
Previous Message PostgreSQL Bugs List 2004-06-27 15:40:50 BUG #1184: listeners not cleaned on crash