On 9/18/07, Ken Logan <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, 2007-09-18 at 11:10 -0700, Alan Hodgson wrote:
>
> On Tuesday 18 September 2007 10:30, Ken Logan <[EMAIL PROTECTED]> wrote:>
> When we try to drop the table we get the error:> ERROR: "member_pkey" is an
> index
> You have to remove t
On Tue, 2007-09-18 at 11:10 -0700, Alan Hodgson wrote:
> On Tuesday 18 September 2007 10:30, Ken Logan <[EMAIL PROTECTED]> wrote:
> > When we try to drop the table we get the error:
> > ERROR: "member_pkey" is an index
>
> You have to remove the table from it's Slony set before you can drop it.
On Tuesday 18 September 2007 10:30, Ken Logan <[EMAIL PROTECTED]> wrote:
> When we try to drop the table we get the error:
> ERROR: "member_pkey" is an index
You have to remove the table from it's Slony set before you can drop it.
Slony does some hackish things to subscriber tables that make the
We are using postgresql 8.2.3 with slony1 1.2.8 and we're having
problems trying to drop a table on the slony1 secondary that was
sucessfully dropped on the master database.
I'm sure this is just because I'm missing something, but it doesn't seem
like there should be any reason the table cannot b
