| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | David Parker <dparker(at)tazznetworks(dot)com> |
| Cc: | postgres general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_listener records |
| Date: | 2005-05-26 18:51:00 |
| Message-ID: | 1117133460.31821.347.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 records hanging
> 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 latest version.
I'm pretty sure the problem you speak of was in fact fixed in later
versions, btw.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Parker | 2005-05-26 18:56:38 | Re: pg_listener records |
| Previous Message | gabriele zelasco | 2005-05-26 18:47:11 | Locking rows |