"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
pgsql-bugs by date
|Next:||From: Kris Jurka||Date: 2004-06-27 23:07:43|
|Subject: PREPARE(d) statements and modifying columns|
|Previous:||From: PostgreSQL Bugs List||Date: 2004-06-27 15:40:50|
|Subject: BUG #1184: listeners not cleaned on crash|