| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Dmitriy Igrishin <dmitigr(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Feature request - CREATE TYPE ... WITH OID = oid_number. |
| Date: | 2010-12-07 17:37:08 |
| Message-ID: | 24583.1291743428@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Tue, Dec 7, 2010 at 11:49 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Say what? He didn't say that, he said "don't assume that user-defined
>> types have hard-wired OIDs".
> Well, you're right, strictly speaking. Of course, the OP is not
> assuming it, he is enforcing it.
No, he's wishing he could enforce it. Which will work, mostly, until
the day it doesn't because of a pre-existing collision. And then he'll
be up the creek with a lot of software that he can't fix readily. I
concur with Andrew's advice: don't go there in the first place. Use a
cache to mitigate the costs of looking up user-defined OIDs, and you
won't regret it later.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-12-07 17:46:27 | Re: pg_execute_from_file review |
| Previous Message | Merlin Moncure | 2010-12-07 17:30:35 | Re: Feature request - CREATE TYPE ... WITH OID = oid_number. |