pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark Lewis <mark.lewis@mir3.com>
To: Ruben Rubio <ruben@rentalia.com>
Cc: Bill Moran <wmoran@collaborativefusion.com>
Cc: Chris Mair <chris@1006.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: [Solved] Postgres performance problem
Date: Thu, 30 Aug 2007 11:08:47 -0700
Message-ID: <1188497327.22730.160.camel@archimedes> (raw)
In-Reply-To: <46D692CC.7010907@rentalia.com>
References: <46D2B879.6010308@rentalia.com>
	<46D2C4AF.8090501@1006.org>
	<20070827092935.be819c94.wmoran@collaborativefusion.com>
	<46D67730.10505@rentalia.com>
	<46D692CC.7010907@rentalia.com>

Perhaps you had a long-running transaction open (probably a buggy or
hung application) that was preventing dead rows from being cleaned up.
Restarting PG closed the offending connection and rolled back the
transaction, which allowed vacuum to clean up all the dead rows.

If you're not running regular VACUUMs at all but are instead exclusively
running VACUUM FULL, then I don't think you would see warnings about
running out of fsm enties, which would explain why you did not notice
the bloat.  I haven't confirmed that though, so I might be wrong.

-- Mark Lewis

On Thu, 2007-08-30 at 11:50 +0200, Ruben Rubio wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> 
> Hi ...
> 
> Seems its solved. But the problem is not found.
> 
> As you may know, I do a vacuum full and a reindex database each day. I
> have logs that confirm that its done and I can check that everything was
>  fine.
> 
> So, this morning, I stopped the website, I stopped database, started it
> again. (I was around 200  days without restarting), then I vacuum
> database and reindex it (Same command as everyday) . Restart again, and
> run again the website.
> 
> Now seems its working fine. But I really does not know where is the
> problem. Seems vacuum its not working fine?  Maybe database should need
> a restart? I really don't know.
> 
> Does someone had a similar problem?
> 
> Thanks in advance,
> Ruben Rubio
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFG1pLMIo1XmbAXRboRAqgQAKCkWcZYE8RDppEVI485wDLnIW2SfQCfV+Hj
> e8PurQb2TOSYDPW545AJ83c=
> =dQgM
> -----END PGP SIGNATURE-----
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
> 
>                http://archives.postgresql.org



view thread (36+ messages)  latest in thread

Message-ID: <1188497327.22730.160.camel@archimedes>
Permalink:  ../1188497327.22730.160.camel@archimedes/
Also on:    postgresql.org/message-id/1188497327.22730.160.camel@archimedes

 · 

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-performance@postgresql.org
  Cc: mark.lewis@mir3.com, ruben@rentalia.com, wmoran@collaborativefusion.com, chris@1006.org
  Subject: Re: [Solved] Postgres performance problem
  In-Reply-To: <1188497327.22730.160.camel@archimedes>

* 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