From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Subject: Re: Indexes and Primary Keys on Rapidly Growing Tables
Date: Mon, 20 Feb 2012 15:30:06 -0800
Message-ID: <4F42D77E.1050504@agliodbs.com> (raw)
In-Reply-To: <CAAB3BBK8-f3R16LwjDJS3i+Kp8nj6-bOob+L=x5F4DmKk+aisA@mail.gmail.com>
References: <CAAB3BBK8-f3R16LwjDJS3i+Kp8nj6-bOob+L=x5F4DmKk+aisA@mail.gmail.com>
On 2/20/12 2:06 PM, Alessandro Gagliardi wrote:
> . But first I just want to know if people
> think that this might be a viable solution or if I'm barking up the wrong
> tree.
Batching is usually helpful for inserts, especially if there's a unique
key on a very large table involved.
I suggest also making the buffer table UNLOGGED, if you can afford to.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
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: josh@agliodbs.com
Subject: Re: Indexes and Primary Keys on Rapidly Growing Tables
In-Reply-To: <4F42D77E.1050504@agliodbs.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