| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:40:35 |
| Message-ID: | 4CEAAB13.7090603@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/22/2010 12:21 PM, Tom Lane wrote:
> Andrew Dunstan<andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-11-22 17:46:42 | Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files) |
| Previous Message | Tom Lane | 2010-11-22 17:30:20 | Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files) |