Re: dblink versus long connection strings

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: dblink versus long connection strings
Date: 2010-11-22 17:08:24
Message-ID: 28963.1290445704@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2010-11-22 17:12:41 Re: dblink versus long connection strings
Previous Message Tom Lane 2010-11-22 17:07:03 Re: directory archive format for pg_dump