From: Scott Marlowe <scott.marlowe@gmail.com>
To: firerox@centrum.cz
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: slow full table update
Date: Wed, 12 Nov 2008 15:58:49 -0700
Message-ID: <dcc563d10811121458t63499067ucd50e287d5c24a0@mail.gmail.com> (raw)
In-Reply-To: <200811122347.21602@centrum.cz>
References: <200811101728.3048@centrum.cz>
<200811101729.14977@centrum.cz>
<200811101730.15902@centrum.cz>
<dcc563d10811121255h7d788032v4a8aa24c9db523b8@mail.gmail.com>
<200811122347.21602@centrum.cz>
This is the critical point. You have this line:
There were 132969 unused item pointers.
Which says there's 132k or so dead rows in your table. Which means
vacuum / autovacuum isn't keeping up. Did you try and stop the update
several times? Each time it starts then gets killed it creates dead
rows.
Try doing a vacuum full followed by a reindex OR a cluster on this
table and see if that helps.
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: scott.marlowe@gmail.com, firerox@centrum.cz
Subject: Re: slow full table update
In-Reply-To: <dcc563d10811121458t63499067ucd50e287d5c24a0@mail.gmail.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