Nigel Bishop <nigel.bishop@xxxxxxxxx> 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 ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
