pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: codeWarrior <gpatnude@hotmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: DB Cluster hanging
Date: Thu, 13 Oct 2005 11:31:09 -0500
Message-ID: <1129221069.29961.199.camel@state.g2switchworks.com> (raw)
In-Reply-To: <dilvje$13nr$1@news.hub.org>
References: <7e974e490510130822q3a853039n4c96991179deae5a@mail.gmail.com>
	<dilvje$13nr$1@news.hub.org>

If you can't / won't / don't use syslog and want your logs rotated
anyway, look at apache's log rotator.  It works a charm, and rotates
every night at midnight the way I use it.  Quite simple to set up and
very reliable.

On Thu, 2005-10-13 at 10:48, codeWarrior wrote:
> Are you possibly running logrotate on the postgreSQL server logs ? Logrotate 
> is usually set to signal (SIGHUP) the log owner (in this case -- postgreSQL) 
> after rotating the log file...
> 
> You normally can't just delete the logfiles and expect postgreSQL to 
> continue wherever you left it... you normally need to pg_ctl reload or 
> pg_ctl restart after dinking with the log files...
> 
> "Nigel Bishop" <nigel.bishop@gmail.com> wrote in message 
> news:7e974e490510130822q3a853039n4c96991179deae5a@mail.gmail.com...
> > Hi,
> >
> > I'm hoping that someone will be able to answer this query:
> >
> > 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.
> >
> > Eventually I had to issue a kill -9 on the postmaster, set
> > log_statement_stats to false and restarted the cluster, It recovered
> > itself and the data load carried on.
> >
> > My question is, is this normal behaviour when the logfile destination
> > fills up?  There was nothing in the logfile being used at the time of
> > the hang, just stats data.
> >
> > PG version 8.0.3 with archived WAL logs enabled
> >
> > O/S version RH ES4 with 2 CPUs & 2Gb RAM
> >
> > Thanks very much for any input.
> >
> >
> > Regards,
> >
> > Nigel Bishop
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: explain analyze is your friend
> > 
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
> 
>                http://archives.postgresql.org



view thread (7+ messages)  latest in thread

Message-ID: <1129221069.29961.199.camel@state.g2switchworks.com>
Permalink:  ../1129221069.29961.199.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1129221069.29961.199.camel@state.g2switchworks.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: smarlowe@g2switchworks.com, gpatnude@hotmail.com
  Subject: Re: DB Cluster hanging
  In-Reply-To: <1129221069.29961.199.camel@state.g2switchworks.com>
  References: <7e974e490510130822q3a853039n4c96991179deae5a@mail.gmail.com> <dilvje$13nr$1@news.hub.org> <1129221069.29961.199.camel@state.g2switchworks.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox