Re: Bug in pg_describe_object

Alvaro Herrera <alvherre@commandprompt.com>

From: Alvaro Herrera <alvherre@commandprompt.com>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Joel Jacobson <joel@gluefinance.com>, Tom Lane <tgl@sss.pgh.pa.us>, Josh Berkus <josh@agliodbs.com>, AndreasKarlsson <andreas@proxel.se>, Magnus Hagander <magnus@hagander.net>, DimitriFontaine <dimitri@2ndquadrant.fr>, Jim Nasby <jim@nasby.net>, pgsql-hackers Hackers <pgsql-hackers@postgresql.org>

Date: 2011-01-11T15:16:35Z

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

Excerpts from Robert Haas's message of mar ene 11 10:52:12 -0300 2011:

> Well, we shouldn't change them randomly or arbitrarily, but improving them is another thing altogether.  I think the contention that any user or application anywhere is depending on the exact textual representation of a pg_amproc entry is exceedingly dubious.  And I think the current messages are flat-out confusing.

Tom also mentioned that the descriptions are translated, so an
application built to parse anything out of the strings is already
broken.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support