On Fri, 21 Sep 2012 at 14:17, Tom Lane wrote:
All of the use-cases I've thought of for wanting to capture stderr
output for it amount to debugging of some form or other, so it's
probably good enough for that to only work in the first logger
incarnation after database start --- but Reinhard is
Peter Eisentraut writes:
> On 9/20/12 11:06 AM, Tom Lane wrote:
>> Well, I would have no objection to changing pg_ctl so that it redirects
>> the postmaster's stdout/stderr when a -l switch is given (actually,
>> I thought it did that already...). I do object to changing the logger's
>> behavior
On 9/20/12 11:06 AM, Tom Lane wrote:
> Well, I would have no objection to changing pg_ctl so that it redirects
> the postmaster's stdout/stderr when a -l switch is given (actually,
> I thought it did that already...). I do object to changing the logger's
> behavior as you suggest, because that wil
On Thu, 20 Sep 2012 at 11:06, Tom Lane wrote:
(I assume you mean pg_ctl not pg_init?)
Yes, sorry for the confusion.
Well, I would have no objection to changing pg_ctl so that it
redirects the postmaster's stdout/stderr when a -l switch is given
(actually, I thought it did that already...).
Reinhard Max writes:
> On Thu, 20 Sep 2012 at 11:06, Tom Lane wrote:
>> Well, I would have no objection to changing pg_ctl so that it
>> redirects the postmaster's stdout/stderr when a -l switch is given
>> (actually, I thought it did that already...).
> Well, going that route forces me to eith
Reinhard Max writes:
> After starting PostgreSQL with pg_init, stdout and stderr of all
> processes are pipes to the logger (as intended), but the logger itself
> still has FDs 1 and 2 open as inherited from pg_init. I think
> requiring the caller of pg_init to redirect them is not practical,
On Thu, 20 Sep 2012 at 10:31, Heikki Linnakangas wrote:
I believe Tom is referring to the removal of silent_mode in 9.2, see
http://archives.postgresql.org/pgsql-general/2011-06/msg00796.php
and
http://archives.postgresql.org/pgsql-hackers/2011-06/msg02156.php.
"We removed logic associated w
On 20.09.2012 00:05, Reinhard Max wrote:
On Wed, 19 Sep 2012 at 12:39, Tom Lane wrote:
reinh...@m4x.de writes:
And what makes /dev/null necessarily the right substitute?
Because it is what virtually all deamons have been doing for the last
3..4 decades?
I don't think we should change this wi
On Wed, 19 Sep 2012 at 12:39, Tom Lane wrote:
reinh...@m4x.de writes:
When initially starting up, syslogger keeps stdout and stderr open
instead of closing them and reopening them from /dev/null for
proper daemonisation.
How exactly could it "close and reopen" them without losing their
ide
reinh...@m4x.de writes:
> When initially starting up, syslogger keeps stdout and stderr open instead
> of closing them and reopening them from /dev/null for proper daemonisation.
How exactly could it "close and reopen" them without losing their
identity? And what makes /dev/null necessarily the r
The following bug has been logged on the website:
Bug reference: 7559
Logged by: Reinhard Max
Email address: reinh...@m4x.de
PostgreSQL version: 9.1.5
Operating system: openSUSE
Description:
When initially starting up, syslogger keeps stdout and stderr open instead
of
11 matches
Mail list logo
