From: Reuven M. Lerner <reuven@lerner.co.il>
To: Samuel Gendler <sgendler@ideasculptor.com>
Cc: Glyn Astill <glynastill@yahoo.co.uk>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Very long deletion time on a 200 GB database
Date: Fri, 24 Feb 2012 14:37:30 +0200
Message-ID: <4F47848A.20800@lerner.co.il> (raw)
In-Reply-To: <CAEV0TzB=zeYBO_T-kcKgcSA4DwRJ6Ka5MPfDhZ_hZ8pWc40QbA@mail.gmail.com>
References: <4F45FB55.1020600@lerner.co.il>
<1329990620.15378.YahooMailNeo@web171403.mail.ir2.yahoo.com>
<4F4730B4.2050602@lerner.co.il>
<CAEV0TzB=zeYBO_T-kcKgcSA4DwRJ6Ka5MPfDhZ_hZ8pWc40QbA@mail.gmail.com>
Hi, everyone. Samuel wrote:
>
> What is work_mem set to? If all the other values were set so low, I'd
> expect work_mem to also be small, which could be causing all kind of
> disk activity when steps don't fit into a work_mem segment.
I just checked, and work_mem is set to 30 MB. That seems a bit low to
me, given the size of the database and the fact that we're doing so much
sorting and subselecting. Am I right that we should push that up some more?
Reuven
--
Reuven M. Lerner -- Web development, consulting, and training
Mobile: +972-54-496-8405 * US phone: 847-230-9795
Skype/AIM: reuvenlerner
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: reuven@lerner.co.il, sgendler@ideasculptor.com, glynastill@yahoo.co.uk
Subject: Re: Very long deletion time on a 200 GB database
In-Reply-To: <4F47848A.20800@lerner.co.il>
* 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