Re: obj_unique_identifier(oid)

Joel Jacobson <joel@gluefinance.com>

From: Joel Jacobson <joel@gluefinance.com>

To: Dimitri Fontaine <dimitri@2ndquadrant.fr>

Cc: Robert Haas <robertmhaas@gmail.com>, Jim Nasby <jim@nasby.net>, Herrera Alvaro <alvherre@commandprompt.com>, pgsql-hackers Hackers <pgsql-hackers@postgresql.org>

Date: 2011-01-08T13:05:17Z

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 →

Add pg_describe_object function
- 6cc2deb86e91 9.1.0 cited

2011/1/8 Dimitri Fontaine <dimitri@2ndquadrant.fr>:
>  http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6cc2deb86e9183262493a6537700ee305fb3e096

Nice! Has the patch been accepted and will be made available in future
versions of pg?

Also, why return NULL for pinned objects? They can also be described
using a unique identifier.
(+   /* for "pinned" items in pg_depend, return null */)

It is useful to describe such objects to be able to diff different
versions of pg, i.e. comparing which pinned objects exists, doing so
can tell you the odds for an application depending on certain pinned
objects being compatible with a specific version of the database.

-- 
Best regards,

Joel Jacobson
Glue Finance