From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Nigel Bishop <nigel(dot)bishop(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: DB Cluster hanging |
Date: | 2005-10-13 16:12:08 |
Message-ID: | 23010.1129219928@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Nigel Bishop <nigel(dot)bishop(at)gmail(dot)com> writes:
> Last night at 3am our Postgresql DB cluster hung. At the time data
> was being loaded. The parameter log_statement_stats in the
> postgresql.conf file was set to true. This was churning out data into
> the logfile which was switching every 10Mb. Eventually the partition
> where the logfiles are written to filled up fair enough this had
> been going on since about 5.30pm the previous evening and the logfiles
> were being generated at the rate of 4/5 a minute. The partition was
> cleared of old logs and I expected the DB to spring in to life, but no
> it just sat there. I could not connect with psql or pg_ctl to
> shutdown the cluster.
How was the logging being done exactly? syslog? redirect_stderr?
If redirect_stderr, this could well be a PG bug --- I kinda doubt
anyone has tested that scenario.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-10-13 16:12:50 | Re: Urgent! |
Previous Message | Bruce Momjian | 2005-10-13 15:56:48 | Re: Urgent! |