Try the copytruncate directive in the logrotate configuration file. (See 'man
logrotate'). This should allow it to work without restarting postgresql. But as the
man file says, there is a small chance of losing some log entries.
On Wed, Mar 07, 2001 at 10:37:30AM -0500, root wrote:
> Be sure
Thank you anyway.
I have solve my problem in 6.5.3 (too old server) by
creating pg_options
verbose=2
query=1
syslog=0
hostlookup
showportnumber
I
I set syslog=0 'coz I can't make it log to /var/log/postgresql.
I removed "-d 2" in /etc/rc.d/init.d/postgresql:
su -l postgre
Be sure to stop postgres, rotate your log (or move it out of the /var/log
directory and then rotate it), and restart postgresql. That will solve your
problem. Hopefully you don't need a 24x7 available database as this might take
a few seconds for your server to complete.
On Wed, 07 Mar 2001, Wi
Thank you anyway.
I have solve my problem in 6.5.3 (too old server) by
creating pg_options
verbose=2
query=1
syslog=0
hostlookup
showportnumber
I
I set syslog=0 'coz I can't make it log to /var/log/postgresql.
I removed "-d 2" in /etc/rc.d/init.d/postgresql:
su -l postgre
[EMAIL PROTECTED] writes:
>William L James writes:
>
>> script - su -l postgresql -c "/usr/bin/pg_ctl -D $PGDATA -p
>> /usr/bin/postmaster start >>/var/log/postgresql 2>&1"), but
>> when the weekly logrotate.d function kicks in, Postgres logging
>> stops.
>
>The logging probably continues to go to
Peter Eisentraut wrote:
> William L James writes:
> > script - su -l postgresql -c "/usr/bin/pg_ctl -D $PGDATA -p
> > /usr/bin/postmaster start >>/var/log/postgresql 2>&1"), but
> > when the weekly logrotate.d function kicks in, Postgres logging
> > stops.
> The logging probably continues to go
William L James writes:
> script - su -l postgresql -c "/usr/bin/pg_ctl -D $PGDATA -p
> /usr/bin/postmaster start >>/var/log/postgresql 2>&1"), but
> when the weekly logrotate.d function kicks in, Postgres logging
> stops.
The logging probably continues to go to the rotated-away file. The
typic
Hi there:
We are running PostgreSQL 7.0.2 on RedHat Linux 6.2 and
have encountered a few strange problems that continue to
elude us - namely INSERT and DELETE functions that end
abnormally, but do not include any information as to why (the
JDBC connection just seems to have gone away). Trying to
