Re: dblink versus long connection strings
| От | Tom Lane |
|---|---|
| Тема | Re: dblink versus long connection strings |
| Дата | |
| Msg-id | 29273.1290446496@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: dblink versus long connection strings (Andrew Dunstan <andrew@dunslane.net>) |
| Ответы |
Re: dblink versus long connection strings
Re: dblink versus long connection strings |
| Список | pgsql-hackers |
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.
regards, tom lane
В списке pgsql-hackers по дате отправления: