Tom Lane wrote:
>
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > The real problem with redirecting the postmaster output is the issue
> > of log rolling, which is impossible to do in the 'classic'
> > stderr/stdout redirect UNLESS you throw down postmaster when rolling
> > the log (unless you know
On Mon, 22 May 2000 00:19:45 -0400 Tom Lane wrote:
> There needn't be a lot of code involved, we just need a
> well-thought-out spec for how it should work. Comments anyone?
I run postmaster under Dan Bernstein's "daemontools", which include
logging facilities:
http://cr.yp.to/daemon
Lamar Owen <[EMAIL PROTECTED]> writes:
> The real problem with redirecting the postmaster output is the issue
> of log rolling, which is impossible to do in the 'classic'
> stderr/stdout redirect UNLESS you throw down postmaster when rolling
> the log (unless you know a trick I don't).
Yes. I th
On Sun, 21 May 2000, Thomas Good wrote:
> On the GENERAL list the issue of firing up a server, and the silent flag
> used by the default redhatter 'postgresql' script in init.d came up.
Yes, I read the thread. I didn't write the original initscript -- but
hopefully have changed it to more your l
On Sat, 20 May 2000, Lamar Owen wrote:
> The 7.0-2 RPMset fixes the following:
> 1.) SPI headers are now the 7.0 set, and not the 6.5.3 set;
> 2.) pg_options default to NOT enable syslog, or extended query logging, as
> syslogd has some issues with long queries (such as issued by psql's \d
>
The 7.0-2 RPMset fixes the following:
1.) SPI headers are now the 7.0 set, and not the 6.5.3 set;
2.) pg_options default to NOT enable syslog, or extended query logging, as
syslogd has some issues with long queries (such as issued by psql's \d
command!);
3.) Alpha patches have returned
