Re: Invalid length of startup packet - Mailing list pgsql-general

From Jan Wieck
Subject Re: Invalid length of startup packet
Date
Msg-id 200205291429.g4TETQL19074@saturn.janwieck.net
Whole thread Raw
In response to Re: Invalid length of startup packet  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Invalid length of startup packet
List pgsql-general
Tom Lane wrote:
> Ron Snyder <snyder@roguewave.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@Yahoo.com #



pgsql-general by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: what do the operator * exactly ?
Next
From: Tom Lane
Date:
Subject: Re: How to cripple a postgres server