Horton

Re: enhanced error fields

Pavel Stehule <pavel.stehule@gmail.com>

View thread
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Peter Geoghegan <peter@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "anarazel@anarazel.de" <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>, Stephen Frost <sfrost@snowman.net>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Alvaro Herrera <alvherre@commandprompt.com>
Date: 2013-01-05T16:56:30Z
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. Create a "sort support" interface API for faster sorting.

2013/1/4 Peter Geoghegan <peter@2ndquadrant.com>:
> On 4 January 2013 18:07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Exactly.  To my mind, the *entire* point of this patch is to remove the
>> need for people to try to dig information out of potentially-localized
>> message strings.  It's not clear to me that we have to strain to provide
>> information that isn't in the currently-reported messages --- we are
>> only trying to make it easier for client-side code to extract the
>> information it's likely to need.
>
> It seems that we're in agreement, then. I'll prepare a version of the
> patch very similar to the one I previously posted, but with some
> caveats about how reliably the values can be used. I think that that
> should be fine.

is there agreement of routine_name and trigger_name fields?

Regards

Pavel

>
> --
> Peter Geoghegan       http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training and Services