Horton

Re: describe objects, as in pg_depend

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2010-11-17T15:20:06Z
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. has_table_privilege spawns scions has_database_privilege, has_function_privilege,

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> A customer of ours (Enova Financial) requested the ability to describe
> objects in pg_depend.  The wiki contains a simplistic SQL snippet that
> does the task, but only for some of the object types, and it's rather
> ugly.  It struck me that we could fulfill this very easily by exposing
> the getObjectDescription() function at the SQL level, as in the attached
> module.

What's the point of the InvalidOid check?  It seems like you're mostly
just introducing a corner case: sometimes, but not always, the function
will return NULL instead of failing for bad input.  I think it should
just fail always.

			regards, tom lane