From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Jon <polandj(at)engin(dot)umich(dot)edu> |
Cc: | Justin Clift <justin(at)postgresql(dot)org>, <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: debug_level 0 does not stop debug messages |
Date: | 2001-05-03 16:25:49 |
Message-ID: | Pine.LNX.4.30.0105031823150.900-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Jon writes:
> I'm not using pg_ctl, I'm using postmaster directly. So, in my case I
> tried passing "-d0" to it, but it had no effect. Command line:
>
> postmaster -i -d0 -D /var/pgsql/data -c syslog=2
>
> Any ideas? I could patch the code to remove the excessive elog's in the
> vacuum command, but I'd rather understand how elog interacts with the
> global DebugLvl variable.
The "interaction" is completely ad hoc, i.e., the code is free to write
anything to the log and completely ignore the debug level. I agree that
there should be a more systematic approach to what gets logged.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
From | Date | Subject | |
---|---|---|---|
Next Message | Jon | 2001-05-03 16:28:25 | Re: debug_level 0 does not stop debug messages |
Previous Message | Piers Scannell | 2001-05-03 16:20:58 | RE: Found an example prooving bug |