Re: Some strange bug with drop table with slony cluster

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Maxim Boguk <mboguk(at)masterhost(dot)ru>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Some strange bug with drop table with slony cluster
Date: 2009-06-17 23:07:59
Message-ID: dcc563d10906171607t62b651dcw8c5c7c31b51eabb7@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2009/6/17 Maxim Boguk <mboguk(at)masterhost(dot)ru>:
> DB version: PostgreSQL 8.3.6 (under linux)
> no server/db crashes happen before.
>
> Server was slave in slony replication.
>
> Now problem:
> table was unsubscribed from replication (without any errors)
> and then dropped from master without any errors
>
> But when i try drop table from slave i got very strange error:

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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-06-17 23:18:51 Re: Some strange bug with drop table with slony cluster
Previous Message Tom Lane 2009-06-17 23:05:35 Re: issue with lo_lseek - it returns 4