Sorry, a couple of things that I intended to mention in my initial post
- I must have forgotten.
1) We (actually I) compiled Postgres from source.
2) The relevant section of the config file looks like this:
#log_destination = 'stderr'
logging_collector = on
log_directory = '/var/log/postgres'
log_filename = 'postgresql-%Y-%m-%d.log'
#log_truncate_on_rotation = off
log_rotation_age = 7d
#log_rotation_size = 10MB
3) If I issue ls -l I see the following (last few lines only):
2009-06-03 19:55 postgresql-2009-05-28.log
2009-06-03 23:32 postgresql-2009-06-03.log
2009-06-04 15:46 postgresql-2009-06-04.log
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
-------------------------------------------------------
For a free subscription to the Seton Home Study School monthly
electronic newsletter, send an e-mail to newsletter-sub@xxxxxxxxxxxxx
-------------------------------------------------------
Tom Lane wrote:
Lewis Kapell <lkapell@xxxxxxxxxxxxx> writes:
This is a really strange one. We are running PostgreSQL 8.3.7 on a
Fedora Core 8 system (uname -a gives: 2.6.23.1-42.fc8).
On Wednesday I was reading about the upcoming change in the default
value of default_statistics_target from 10 to 100 - we had never changed
this value, so I bumped it up a bit and also changed the value of
log_autovacuum_min_duration so that I could monitor the results.
Yesterday I tweaked the settings a bit more and continued to monitor the
logs. About two hours later, the log file stopped growing.
Are you watching the right log file? I believe most Fedora packagings
of PG are set up to rotate log output among multiple files. In any
case it's hard to diagnose this without knowing what logging settings
you're using.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
