Horton

Re: obj_unique_identifier(oid)

Joel Jacobson <joel@gluefinance.com>

View thread
From: Joel Jacobson <joel@gluefinance.com>
To: Joel Jacobson <joel@gluefinance.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2011-01-07T19:59:09Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add pg_describe_object function

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.