From: | Fred Yankowski <fred(at)ontosys(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | command-line option for logfile |
Date: | 2001-02-05 17:18:15 |
Message-ID: | 20010205111815.B18161@enteract.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
A command-line option for specifying the logfile would be very helpful
on WIN32.
When setting up PostgreSQL to run as an NT service, the only way I can
see to redirect stdout/stderr to a file is to invoke postmaster via a
wrapper sh/bash process. I suspect that this wrapper process would
have to hang around as long as postmaster is running, although it
might be possible to do an exec to overlay it. It would be nice to
avoid this wrapper process.
On Mon, Feb 05, 2001 at 06:01:10PM +0100, Peter Eisentraut wrote:
> > > There should be an option to put the server log somewhere, either a file
> > > or maybe a pipe, e.g.,
> > > pg_ctl -l logfile
> > > pg_ctl -P 'magic-log-rotator -x -y -z'
> >
> > Or we could just switch over to syslog as the standard log
> > destination...
>
> Not as long as all the good stuff goes to stderr.
--
Fred Yankowski fred(at)OntoSys(dot)com tel: +1.630.879.1312
Principal Consultant www.OntoSys.com fax: +1.630.879.1370
OntoSys, Inc 38W242 Deerpath Rd, Batavia, IL 60510, USA
From | Date | Subject | |
---|---|---|---|
Next Message | Mathieu Dube | 2001-02-05 17:20:45 | Re: Re: 1024 limits?? |
Previous Message | Fred Yankowski | 2001-02-05 17:04:05 | build WIN32 ODBC using VC++, not Cygwin/gcc |