Scott Marlowe 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 sum
2009/6/17 Maxim Boguk :
> 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
Maxim Boguk writes:
> 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:
> hh=# drop TABLE metro_station_old;
> ERR
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
