On Mon, 15 Mar 2004, Bruce Momjian wrote:
> scott.marlowe wrote:
> > On Thu, 11 Mar 2004, Christopher Kings-Lynne wrote:
> >
> > > > You could also consider not using syslog at all: let the postmaster
> > > > output to its stderr, and pipe that into a log-rotation program.
> > > > I believe some people use Apache's log rotator for this with good
> > > > results.
> > >
> > > Not an option I'm afraid. PostgreSQL just jams and stops logging after
> > > the first rotation...
> > >
> > > I've read in the docs that syslog logging is the only "production"
> > > solution...
> >
> > Can you use the apache log rotator? It's known to work in my environment
> > (redhat 7.2, postgresql 7.2 and 7.4) with this command to start it in my
> > rc.local file:
> >
> > su - postgres -c 'pg_ctl start | rotatelogs $PGDATA/pglog 86400 2>1&'
>
> Sure, our documentation specifically mentions using rotatelogs.
hehe. What I meant was can Christopher use it, or does he have a
limitation in his environment where he can't get ahold of the apache log
rotater... :-)
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
