Re: obj_unique_identifier(oid) - Mailing list pgsql-hackers

From Joel Jacobson
Subject Re: obj_unique_identifier(oid)
Date
Msg-id 3615046013433274531@iso-8859-1msgid
Whole thread Raw
In response to Re: obj_unique_identifier(oid)  (Joel Jacobson <joel@gluefinance.com>)
List 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@gluefinance.com> wrote:

> Sent from my iPhone
>
> On 7 jan 2011, at 20:46, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
>> Joel Jacobson <joel@gluefinance.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.


pgsql-hackers by date:

Previous
From: Joel Jacobson
Date:
Subject: Re: obj_unique_identifier(oid)
Next
From: Robert Haas
Date:
Subject: Re: crash-safe visibility map, take three