Re: Any reason why the default_with_oids GUC is still there? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Any reason why the default_with_oids GUC is still there?
Date
Msg-id 10964.1285108825@sss.pgh.pa.us
Whole thread Raw
In response to Re: Any reason why the default_with_oids GUC is still there?  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Tom Lane wrote:
>> Actually, I can think of a fairly sizable reason not to remove it:
>> pg_dump issues "SET default_with_oids" commands in its scripts, and
>> has done for lo these many years.  So you'd be breaking backwards
>> compatibility with even-quite-recent dumps.

> Also, doesn't some SQL standard require oids, so we should have a way to
> enable them by default for all tables?

Seems highly unlikely.  If there is any requirement for unique row
identifiers in the spec, OIDs as currently implemented likely wouldn't
meet it anyway.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Any reason why the default_with_oids GUC is still there?
Next
From: "Kevin Grittner"
Date:
Subject: Re: Get the offset of a tuple inside a table