Re: ALTER TABLE .. SET WITH / WITHOUT OIDS - Mailing list pgsql-patches

From Christopher Kings-Lynne
Subject Re: ALTER TABLE .. SET WITH / WITHOUT OIDS
Date
Msg-id GNELIHDDFBOCMGBFGEFOAEPACEAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: ALTER TABLE .. SET WITH / WITHOUT OIDS  (Neil Conway <neilc@samurai.com>)
Responses Re: ALTER TABLE .. SET WITHOUT OIDS -- ROUND 2  (Rod Taylor <rbt@rbt.ca>)
List pgsql-patches
I agree.  I want to remove OIDs from heaps of our tables when we go to 7.3.
I'd rather not have to do it in the dump due to down time.

Chris

> -----Original Message-----
> From: pgsql-patches-owner@postgresql.org
> [mailto:pgsql-patches-owner@postgresql.org]On Behalf Of Neil Conway
> Sent: Thursday, 9 January 2003 10:58 AM
> To: Tom Lane
> Cc: Rod Taylor; PostgreSQL Patches
> Subject: Re: [PATCHES] ALTER TABLE .. SET WITH / WITHOUT OIDS
>
>
> On Thu, 2003-01-02 at 18:08, Tom Lane wrote:
> > I can see some value in the SET WITHOUT OIDS half of the patch, as this
> > gives a way of reclaiming space in a table that was unthinkingly created
> > with OIDs.  But I'm not sure we should expend the code space to provide
> > just a one-way transformation.
>
> IMHO, it's still worth having this part of the patch, even if the
> transformation is only one-way.
>
> Cheers,
>
> Neil
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>


pgsql-patches by date:

Previous
From: Neil Conway
Date:
Subject: Re: ALTER TABLE .. SET WITH / WITHOUT OIDS
Next
From: Neil Conway
Date:
Subject: Re: updated PITR patch