pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kenneth Marshall <ktm@rice.edu>
To: Scott Whitney <swhitney@journyx.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_clogs hanging around
Date: Thu, 10 Mar 2011 07:47:23 -0600
Message-ID: <20110310134723.GX8169@aart.is.rice.edu> (raw)
In-Reply-To: <11997393.14072.1299762070874.JavaMail.root@zimbra.int.journyx.com>
References: <358079.14070.1299761935620.JavaMail.root@zimbra.int.journyx.com>
	<11997393.14072.1299762070874.JavaMail.root@zimbra.int.journyx.com>

On Thu, Mar 10, 2011 at 07:01:10AM -0600, Scott Whitney wrote:
> Ooops...I accidentally took this off list, as Kevin was nice enough to point out.
> 
> 
> >> What am I looking for? 
> 
> >Outliers. 
> 
> > Yeah. It's just those 2. I'd assume that the db I created
> > yesterday would be an outlier, but template0 has been there all along
> > (of course) and is still listed as 648, a significantly smaller number. 
> 
> 
> >> The output shows me 345 rows, most of which are 132xxxxx numbers. 
> >> Two of them (template0 and a database created yesterday) say 648. 
> 
> >The template0 database is what's keeping the clog files from being 
> >cleaned up, but I guess the big question is why you care. They will 
> >go away eventually, and shouldn't affect performance. Are they 
> >taking enough space to merit extraordinary effort to clean them up? 
> > -Kevin 
> 
> 
> My concern is that when we had a failure a few years ago, and one of the clog files went bad. I had to manually recreate some customer data after bringing up the previous backup. So, I'd rather have them not there, because, well, if there are 200 of them in the dir, there's a higher chance in a case of a crash that one goes bad than if I have 15. 
> 
> Would adding -f (full) clean these up? I seem to recall it did in earlier versions. I've added the -F to it already, and that didn't seem to help. 
> 

If you have hardware problems like that you have way more problems.
You could have corruption (silent) occurring in any of the other database
files. Good luck.

Cheers,
Ken



view thread (12+ messages)  latest in thread

Message-ID: <20110310134723.GX8169@aart.is.rice.edu>
Permalink:  ../20110310134723.GX8169@aart.is.rice.edu/
Also on:    postgresql.org/message-id/20110310134723.GX8169@aart.is.rice.edu

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: ktm@rice.edu, swhitney@journyx.com
  Subject: Re: pg_clogs hanging around
  In-Reply-To: <20110310134723.GX8169@aart.is.rice.edu>

* 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