From: | Jan Wieck <janwieck(at)yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ron Snyder <snyder(at)roguewave(dot)com>, "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>, "'Henrik Steffen'" <steffen(at)city-map(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Invalid length of startup packet |
Date: | 2002-05-29 14:29:26 |
Message-ID: | 200205291429.g4TETQL19074@saturn.janwieck.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Ron Snyder <snyder(at)roguewave(dot)com> writes:
> > If the output becomes something similar to this:
> > May 28 09:14:55 vault pgqv[4332]: [1] DEBUG: connection: host=172.21.41.62:3586
> > May 28 09:14:55 vault pgqv[4332]: [2] DEBUG: authorize: user=dbuser database=test
>
> I kinda like that approach, actually, with both messages driven off the
> LOG_CONNECTIONS flag. Does anyone really hate it?
In addition I would suggest that these two messages are also
printed before the first real elog() output occurs, if that
flag is turned off.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-05-29 15:52:51 | Re: How to cripple a postgres server |
Previous Message | Thomas Lockhart | 2002-05-29 14:11:59 | Re: what do the operator * exactly ? |