Re: invalid search_path complaints
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: 2012-04-03T18:16:01Z
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 →
-
Revise the API for GUC variable assign hooks.
- 2594cf0e8c04 9.1.0 cited
Robert Haas <robertmhaas@gmail.com> writes: > On Tue, Apr 3, 2012 at 12:05 PM, Robert Haas <robertmhaas@gmail.com> wrote: >> On Tue, Apr 3, 2012 at 11:49 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> I would say that's an improvement. Do you think it isn't? >> It seems like a log spam hazard at high connection rates. [ shrug... ] Failing to report a problem is a problem, too. By your argument any error message anywhere should be removed because it might be a "log spam hazard" at high reporting rates. regards, tom lane