| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Maxim Boguk <mboguk(at)masterhost(dot)ru>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Some strange bug with drop table with slony cluster |
| Date: | 2009-06-17 23:18:51 |
| Message-ID: | 6328.1245280731@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> We've run into issues with drop table and slony as well. What version
> of slony are you running? We're running 1.2.14. Latest version in
> that branch in 1.2.16, but we haven't had cause to upgrade to it just
> yet. I'll be looking at 2.0.latest and 1.2.16 over the summer to see
> if one or the other can fix this issue for us.
FWIW, I believe one of the design goals for 2.0 was to get rid of their
direct manipulation of the system catalogs, which should in turn remove
this type of hazard. I don't know the actual status though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Izmailov | 2009-06-18 00:30:00 | Re: issue with lo_lseek - it returns 4 |
| Previous Message | Scott Marlowe | 2009-06-17 23:07:59 | Re: Some strange bug with drop table with slony cluster |