From: Bastian Voigt <post@bastian-voigt.de>
To: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: My quick and dirty "solution" (Re: Performance Problem with Vacuum of bytea table (PG 8.0.13))
Date: Fri, 25 May 2007 16:11:45 +0200
Message-ID: <4656EEA1.8030409@bastian-voigt.de> (raw)
In-Reply-To: <4656E1B5.3020300@archonet.com>
References: <46569E6A.2060509@bastian-voigt.de>
<4656BB5E.3000109@archonet.com>
<4656BEF1.4050609@bastian-voigt.de>
<4656C1C7.3000003@archonet.com>
<4656C411.8010509@bastian-voigt.de>
<4656CDC2.6030106@archonet.com>
<4656D6EC.5060506@bastian-voigt.de>
<4656E1B5.3020300@archonet.com>
Richard Huxton wrote:
> Could you check the output of vacuum verbose on that table and see how
> much work it's doing? I'd have thought the actual bytea data would be
> TOASTed away to a separate table for storage, leaving the vacuum with
> very little work to do.
I'm quite new to postgres (actually I just ported our running
application from MySQL...), so I don't know what toast means. But I
noticed that vacuum also tried to cleanup some "toast" relations or so.
This was what took so long.
> It might well be your actual problem is your disk I/O is constantly
> saturated and the vacuum just pushes it over the edge. In which case
> you'll either need more/better disks or to find a quiet time once a
> day to vacuum and just do so then.
Yes, that was definitely the case. But now everything runs smoothly
again, so I don't think I need to buy new disks.
Regards
Bastian
--
Bastian Voigt
Neumünstersche Straße 4
20251 Hamburg
telefon +49 - 40 - 67957171
mobil +49 - 179 - 4826359
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: post@bastian-voigt.de, dev@archonet.com
Subject: Re: My quick and dirty "solution" (Re: Performance Problem with Vacuum of bytea table (PG 8.0.13))
In-Reply-To: <4656EEA1.8030409@bastian-voigt.de>
* 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