| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | daniel alvarez <d-alvarez(at)gmx(dot)de> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: OIDs as keys |
| Date: | 2003-02-26 16:10:13 |
| Message-ID: | 200302261610.13115.dev@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wednesday 26 Feb 2003 2:59 pm, daniel alvarez wrote:
>
> Why should user-defined tables have OIDs by default? Other DBMS use ROWIDs
> as the physical storage location used for pointers in index leafs, but this
> is equivalent
> to Postgres TIDs. To the user an OID column is not different than any other
> column
> he can define himself. I'd find it more natural if the column wasn't there
> at all.
I believe the plan is to phase them out, but some people are using them, so
the default is still to create them. Imagine if you were using OIDs as keys
and after a dump/restore they were all gone...
--
Richard Huxton
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-02-26 17:17:24 | Re: OIDs as keys |
| Previous Message | Tom Lane | 2003-02-26 16:02:30 | Re: OIDs as keys |