| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Any reason why the default_with_oids GUC is still there? |
| Date: | 2010-09-21 22:40:25 |
| Message-ID: | 10964.1285108825@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-09-21 22:47:53 | Re: Get the offset of a tuple inside a table |
| Previous Message | Bruce Momjian | 2010-09-21 22:31:43 | Re: Any reason why the default_with_oids GUC is still there? |