From: Mark Stosberg <mark@summersault.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: debugging handle exhaustion and 15 min/ 5mil row delete
Date: Fri, 7 May 2010 10:10:31 -0400
Message-ID: <20100507101031.3442dd08@summersault.com> (raw)
In-Reply-To: <4BE3C4C9.60601@uci.cu>
References: <20100507093742.20c715b1@summersault.com>
<4BE3C4C9.60601@uci.cu>
> You can use TRUNCATE instead DELETE. TRUNCATE is more efficient and
> faster that DELETE.
Thanks for the suggestion. However, TRUNCATE is not compatible with
Slony, and we also have some rows which remain in table.
> Now, we need more information about your system to give you a certain
> solution:
> Are you using a RAID controller for you data?
Yes.
> Do you have separated the xlog directory from the data directory?
No.
> Which is your Operating System?
FreeBSD.
> Which is you architecture?
i386.
Thanks for the feedback. I'm going to try batching the deletes for now,
which is approach was worked well for some of our other long-running
deletes.
Mark
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@summersault.com
Subject: Re: debugging handle exhaustion and 15 min/ 5mil row delete
In-Reply-To: <20100507101031.3442dd08@summersault.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