Re: [PATCHES] log session end - again

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] log session end - again
Date: 2004-02-05 13:48:30
Message-ID: 200402051348.i15DmUY16787@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > Right. And if we have sessionids we would want them logged there, I
> > think. And that would rule out anything based on xid or backend pid.
>
> Uh, what's wrong with backend pid? Since we fork before we start doing
> anything with a connection, it should surely be available soon enough
> for the connection log message.
>
> Larry's idea about combining PID and backend start time didn't sound too
> unreasonable to me.

Wow, like the idea too --- pid plus time_t start time of backend.
Actully, it would be good to have star time first so you can sort
everything in order of start time.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2004-02-05 14:05:53 Vacuum Delay feature
Previous Message Zeugswetter Andreas SB SD 2004-02-05 11:45:32 Re: [HACKERS] Sync vs. fsync during checkpoint

Browse pgsql-patches by date

  From Date Subject
Next Message Jan Wieck 2004-02-05 14:05:53 Vacuum Delay feature
Previous Message Claudio Natoli 2004-02-05 13:27:34 CYGWIN correction; ipci rationalization