From: Shaun Thomas <sthomas@optionshouse.com>
To: Stefan Keller <sfkeller@gmail.com>
Cc: Ivan Voras <ivoras@freebsd.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Inserts in 'big' table slowing down the database
Date: Tue, 2 Oct 2012 10:09:10 -0500
Message-ID: <506B0396.4030805@optionshouse.com> (raw)
In-Reply-To: <CAFcOn2_zpBQ1Tky_vHOkBGMLwjHJFdNSUgyZhkg-i3b8-WWMLA@mail.gmail.com>
References: <CAFcOn2_W6v_vqwomCf6DEtXk=N8iB5WU-7XEdcYgX-VFUE32+Q@mail.gmail.com>
<k223s0$e83$1@ger.gmane.org>
<CAFcOn2_zpBQ1Tky_vHOkBGMLwjHJFdNSUgyZhkg-i3b8-WWMLA@mail.gmail.com>
On 10/01/2012 07:15 PM, Stefan Keller wrote:
> Any ideas? Partitioning?
Yes. Make sure you have a good column to partition on. Tables this large
are just bad performers in general, and heaven forbid you ever have to
perform maintenance on them. We had a table that size, and simply
creating an index could take upwards of two hours.
If you can't archive any of the table contents, partitioning may be your
only solution. If you have an EDB 9.1, you'll also have less problems
with the legacy issues people had with planning queries using partitions.
Don't go crazy, though. I try to keep it under a couple dozen partitions
per table, or under 100M records per partition.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas@optionshouse.com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
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: sthomas@optionshouse.com, sfkeller@gmail.com, ivoras@freebsd.org
Subject: Re: Inserts in 'big' table slowing down the database
In-Reply-To: <506B0396.4030805@optionshouse.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