Re: bug in 7.4 SET WITHOUT OIDs

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>, Rod Taylor <rbt(at)rbt(dot)ca>
Subject: Re: bug in 7.4 SET WITHOUT OIDs
Date: 2004-03-23 06:57:46
Message-ID: 405FDFEA.2070102@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> The problem appears to be that ALTER TABLE SET WITHOUT OIDS doesn't make
> the index on the OID column go away.
>
> I don't have a strong opinion on whether to fix this by forcing a drop
> of the index or by rejecting the ALTER command. Seems like we have to
> do one or the other though.
>
> This is actually just the simplest case of a dependency on the OID
> column... whatever the fix is, it has to handle the general case.

Maybe it needs CASCADE/RESTRICT added?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-03-23 07:03:09 Re: bug in 7.4 SET WITHOUT OIDs
Previous Message Tom Lane 2004-03-23 06:35:57 Re: bug in 7.4 SET WITHOUT OIDs