| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Neil Conway" <neilc(at)samurai(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Rod Taylor" <rbt(at)rbt(dot)ca>, "PostgreSQL Patches" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE .. SET WITH / WITHOUT OIDS |
| Date: | 2003-01-09 02:59:25 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOAEPACEAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)postgresql(dot)org
> [mailto:pgsql-patches-owner(at)postgresql(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2003-01-09 04:21:02 | Re: updated PITR patch |
| Previous Message | Neil Conway | 2003-01-09 02:58:15 | Re: ALTER TABLE .. SET WITH / WITHOUT OIDS |