Re: Indexes and Primary Keys on Rapidly Growing Tables - Mailing list pgsql-performance

From Samuel Gendler
Subject Re: Indexes and Primary Keys on Rapidly Growing Tables
Date
Msg-id CAEV0TzCgEe59_VbNcZH2WixcNP+Eo+aTxeEZ5LM4o8SOabNK7w@mail.gmail.com
Whole thread Raw
In response to Re: Indexes and Primary Keys on Rapidly Growing Tables  (Alessandro Gagliardi <alessandro@path.com>)
Responses Re: Indexes and Primary Keys on Rapidly Growing Tables
List pgsql-performance

On Tue, Feb 21, 2012 at 9:59 AM, Alessandro Gagliardi <alessandro@path.com> wrote:
I was thinking about that (as per your presentation last week) but my problem is that when I'm building up a series of inserts, if one of them fails (very likely in this case due to a unique_violation) I have to rollback the entire commit. I asked about this in the novice forum and was advised to use SAVEPOINTs. That seems a little clunky to me but may be the best way. Would it be realistic to expect this to increase performance by ten-fold?


if you insert into a different table before doing a bulk insert later, you can de-dupe before doing the insertion, eliminating the issue entirely.


pgsql-performance by date:

Previous
From: Alessandro Gagliardi
Date:
Subject: Re: Indexes and Primary Keys on Rapidly Growing Tables
Next
From: Alessandro Gagliardi
Date:
Subject: Re: Indexes and Primary Keys on Rapidly Growing Tables