Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS

From: Marko Kreen <markokr(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, David Fetter <david(at)fetter(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS
Date: 2009-02-09 16:56:33
Message-ID: e51f66da0902090856j3c3ab1f8s7f426093cccd9ebf@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/9/09, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> Marko Kreen wrote:
> > We've set default_with_oids = false, for quite a long time. But there
> > are still tables remaining with oids. And this discussion showed it
> > now easy to get rid of them.
>
> Do you still need the oids? If not, run ALTER TABLE WITHOUT OIDS before
> upgrading to 8.4, while it's still fast. If yes, you couldn't use the option
> to remove them at pg_dump anyway because you still need them after the
> upgrade.

Indeed. I must apologize. I seems I read too fast and got the impression
the bug applies also to older versions of Postgres. If this is not
the case and ALTER still works fine on older versions, most of my comments
do not apply, because indeed, we can clean it up on 8.3.

There is still minor problem that it will be made expensive on 8.4, but
as it is not released yet, it can be solved by advising users to clean
up their tables on 8.3.

--
marko

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2009-02-09 17:01:03 Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS
Previous Message Robert Haas 2009-02-09 16:50:38 Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS