Re: dblink versus long connection strings

Andrew Dunstan <andrew@dunslane.net> writes:
> On 11/22/2010 11:51 AM, Tom Lane wrote:
>> Perhaps a reasonable compromise is to issue the truncation warnings when
>> an overlength name is being *entered* into the connection table, but not
>> for simple lookups.

> Can't we distinguish a name from a conninfo string by the presence of an 
> = sign?

No, because = isn't disallowed in names ...
        regards, tom lane