From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:30:35 |
Message-ID: | AANLkTi=bxMnZ34W=+oGVRqQjmgVoN48F2s4iegKRT5d-@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 7, 2010 at 11:49 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
>> On Tue, Dec 7, 2010 at 10:45 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>>> This doesn't strike me as very good advice. Those things are not exposed
>>> generally for good reason. The right way to do this surely is to have the
>>> app look up and cache the OIDs it needs rather than hardcode the values in
>>> the application.
>
>> Note he didn't provide reasons why he is asking for this power. Your
>> assertion is a coded variant of "don't use the binary protocol" which
>> I happen to think is not very good advice IF you know what you're
>> doing.
>
> 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. And I still think this is a proxy
argument about binary protocol features.
merlin
(Andrew's advice is of course prudent, and should certainly by
typically taken before mine) :-D
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-12-07 17:37:08 | Re: Feature request - CREATE TYPE ... WITH OID = oid_number. |
Previous Message | Andres Freund | 2010-12-07 17:11:46 | Re: Final(?) proposal for wal_sync_method changes |