Re: invalid search_path complaints

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: invalid search_path complaints
Date: 2012-04-03 17:26:25
Message-ID: CA+Tgmoa2b1Uf3KzDH5a7dzC5QKW8WKX56bQNgRfAYhSt0qQf0A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 3, 2012 at 12:05 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Apr 3, 2012 at 11:49 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> If you use ALTER ROLE/DATABASE SET to configure an invalid
>>> search_path, PostgreSQL 9.1 issues a complaint about the invalid
>>> setting on each new connection.  This is a behavior change relatively
>>> to previous releases, which did not.
>>
>> I would say that's an improvement.  Do you think it isn't?
>
> It seems like a log spam hazard at high connection rates.

In particular, you also get a warning in the log every time an autovac
worker starts up. :-(

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-04-03 18:16:01 Re: invalid search_path complaints
Previous Message Robert Haas 2012-04-03 17:20:44 Re: patch for parallel pg_dump