Re: Good way to insert/update when you're not sure of duplicates?

From: Dennis Gearon <gearond(at)fireserve(dot)net>
To: Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in>
Cc: Richard Huxton <dev(at)archonet(dot)com>, Curtis Stanford <curtis(at)stanfordcomputing(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Good way to insert/update when you're not sure of duplicates?
Date: 2003-09-26 15:18:28
Message-ID: 3F7458C4.8090309@fireserve.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

Shridhar Daithankar wrote:

>
> In addition to that, you can try inserting from multiple backends
> simaltenously to speed up the whole process.
>
> And I don't like the modes idea OP gave. I would rather follow
> insert->if-error-update mode in a transaction for each record. And
> fork over say 20/40 parallel backends to achieve good speed.
>
I didn't think mulitple backends worked.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Shridhar Daithankar 2003-09-26 15:44:27 Re: Good way to insert/update when you're not sure of duplicates?
Previous Message Matthew T. O'Connor 2003-09-26 15:17:25 Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)