Re: invalid search_path complaints - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: invalid search_path complaints
Date
Msg-id CAEYLb_U4ZPK4rGR_FdVLuomSwJr1yjnVnsWbVB==+H10_Qr3QA@mail.gmail.com
Whole thread Raw
In response to Re: invalid search_path complaints  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 3 April 2012 19:16, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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.

Surely there's a way to throttle it appropriately?

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: invalid search_path complaints
Next
From: Marko Kreen
Date:
Subject: Re: Speed dblink using alternate libpq tuple storage