Horton

Re: obj_unique_identifier(oid)

Jim Nasby <jim@nasby.net>

View thread
From: Jim Nasby <jim@nasby.net>
To: Joel Jacobson <joel@gluefinance.com>, Herrera Alvaro <alvherre@commandprompt.com>
Cc: pgsql-hackers Hackers <pgsql-hackers@postgresql.org>
Date: 2011-01-07T20:18:41Z
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

On Jan 7, 2011, at 1:46 PM, Tom Lane 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.

BTW, if you're looking at making pg_depnd easier to use, see http://archives.postgresql.org/message-id/1290000774-sup-2218@alvh.no-ip.org
--
Jim C. Nasby, Database Architect                   jim@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net