Thanks. Yeah, I know slony 1.0.5 cleans up after itself, and is better
in general, and I want to get there, but upgrading is not an option at
the moment, unfortunately. Same for postgres 8.
But it still seems like this is something the server itself should be
taking care of, not a client process....
>From: Scott Marlowe [mailto:smarlowe(at)g2switchworks(dot)com]
>Sent: Thursday, May 26, 2005 2:51 PM
>To: David Parker
>Cc: postgres general
>Subject: Re: [GENERAL] pg_listener records
>On Thu, 2005-05-26 at 13:41, David Parker wrote:
>> In failover testing we have been doing recently (postgres 7.4.5 w/
>> slony 1.0.2) we have seen several times when the database comes back
>> up after a power failure it still has old pg_listener
>> around from its previous life. This causes some problems with slony,
>> but of course it is easy enough to implement a procedure to clean
>> those records out, which we have done.
>> But I'm wondering - shouldn't that be part of normal server startup,
>> cleaning out the pg_listener table? Or has this been addressed in
>> 8.X.? Or is there a reason this isn't a good idea?
>You should really be running the latest version of slony,
>1.0.5. There were plenty of little niggling bugs in the
>earlier version that have been fixed. I'd upgrade postgresql
>while I was at it too, but slony DEFINITELY needs to be the
>I'm pretty sure the problem you speak of was in fact fixed in
>later versions, btw.
pgsql-general by date
|Next:||From: Tom Lane||Date: 2005-05-26 19:03:13|
|Subject: Re: maintenance_work_mem upper limit =1gb?? |
|Previous:||From: Scott Marlowe||Date: 2005-05-26 18:51:00|
|Subject: Re: pg_listener records|