Re: On Logging

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: On Logging
Date: 2005-10-01 15:43:34
Message-ID: 20051001154334.GA40138@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 30, 2005 at 06:24:17PM -0700, David Fetter wrote:
> How would per-backend logging work?

I'd suggest having settings for a per-backend 'debug' logging mode that
could be triggered either via a SQL command or a signal to the backend.
It would be useful to be able to log this to a seperate area, based
either on PID or some identifier passed to the sql command. I think this
would cover two use cases:

long-running process that's on one back-end that you want info on (send
signal to that backend)

something using a connection pool. You'd have some one to tell the
application to enable logging based on some set of conditions. When
those conditions were met, logging would be turned on. When a connection
is first grabbed from the connection pool, logging would be forced to
off in case it had been turned on by a previous process (which might
have just disconnected suddenly).
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-10-01 15:44:15 Re: [HACKERS] A Better External Sort?
Previous Message Tom Lane 2005-10-01 15:28:08 Re: Making pgxs builds work with a relocated installation