On Aug 30, 2007, at 2:08 PM, Mark Lewis wrote:
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 th
Decibel! wrote:
On Thu, Aug 30, 2007 at 11:50:04AM +0200, Ruben Rubio wrote:
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, starte
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 regul
On Thu, Aug 30, 2007 at 11:50:04AM +0200, Ruben Rubio wrote:
> 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
> ag
-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,
