From: | Joel Jacobson <joel(at)gluefinance(dot)com> |
---|---|
To: | Joel Jacobson <joel(at)gluefinance(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: obj_unique_identifier(oid) |
Date: | 2011-01-07 19:59:09 |
Message-ID: | 3615046013433274531@unknownmsgid |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The function should take both classid and oid as input. I'll fix.
Sent from my iPhone
On 7 jan 2011, at 20:59, Joel Jacobson <joel(at)gluefinance(dot)com> wrote:
> Sent from my iPhone
>
> On 7 jan 2011, at 20:46, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Joel Jacobson <joel(at)gluefinance(dot)com> writes:
>>> The function obj_unique_identifier(oid) will return a unique name for _any_ oid.
>>
>> Surely this is broken by design? You can *not* assume that the same OID
>> isn't in use for different things in different system catalogs. They're
>> only guaranteed unique within a catalog. That's the main reason why
>> pg_depend has to include the classid.
>>
>> regards, tom lane
>
> Correct. That is why the regclass name (classid) is included in the unique name.
From | Date | Subject | |
---|---|---|---|
Next Message | Joachim Wieland | 2011-01-07 20:18:26 | pg_dump directory archive format / parallel pg_dump |
Previous Message | Joel Jacobson | 2011-01-07 19:57:34 | Re: obj_unique_identifier(oid) |