| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Client application name |
| Date: | 2009-10-21 10:47:39 |
| Message-ID: | 9837222c0910210347w59fee9c3u11f40f75c650959b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 21, 2009 at 11:49, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>> Another idea is to do something similar to the 'prefer' SSL mode, or if
>> the server doesn't support protocol version 3: Try with the GUC in
>> startup packet first, and if that fails, retry without it.
>>
>> I'm not sure if I like either of those better than the extra SET
>> command, but I thought I'd mention it.
>
> The command line sure seems ugly if that's what you meant. Retrying
> doesn't seem so bad, though it'll still litter server logs with
> connection errors.
It'd definitely be good if we can avoid littering the server logs with
it. It's bad enough in some SSL situations already :(
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2009-10-21 10:49:36 | Re: Client application name |
| Previous Message | Simon Riggs | 2009-10-21 10:45:29 | Re: Client application name |