Re: dblink versus long connection strings - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: dblink versus long connection strings
Date
Msg-id 4CEAAB13.7090603@dunslane.net
Whole thread Raw
In response to Re: dblink versus long connection strings  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

On 11/22/2010 12:21 PM, Tom Lane wrote:
> Andrew Dunstan<andrew@dunslane.net>  writes:
>> On 11/22/2010 12:08 PM, Tom Lane wrote:
>>> No, because = isn't disallowed in names ...
>> Ok, true, but it still might not be a bad heuristic to use for issuing a
>> warning on lookup.
> The fine manual says that using "=" in a connection name might be unwise
> because of the risk of confusion.  It doesn't say that you should expect
> to get a NOTICE every single time you use the name.  People have
> complained of postmaster log bloat for lots less reason than this.
>
> In any case I don't see an argument why warning on connection creation
> isn't sufficient.

OK.

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)
Next
From: Robert Haas
Date:
Subject: Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)