Postgres Pro
Downloads
Home   >   mailing lists

Re: Bulk Insert/Update Scenario - Mailing list pgsql-general

From Mana M
Subject Re: Bulk Insert/Update Scenario
Date
Msg-id CAJAiPv5GxqKJ4LsZsXo2Hi9kKCdfqxuNRocVVFwJ1zXTKOK=yQ@mail.gmail.com
Whole thread Raw
In response to Re: Bulk Insert/Update Scenario  (Jordan Deitch <jwdeitch@gmail.com>)
Responses Re: Bulk Insert/Update Scenario  (Jordan Deitch <jwdeitch@gmail.com>)
Re: Bulk Insert/Update Scenario  ("Peter J. Holzer" <hjp-pgsql@hjp.at>)
List pgsql-general
Tree view
Thanks Jordan.

One more question I had was - anyway to avoid doing individual INSERT ... ON CONFLICT? I was thinking about dumping everything into TEMP table and using that as source for INSERT ... ON CONFLICT. However, I was not sure on how to get thousands of rows from my Python application into TEMP table in one shot. Or is there any better alternatives?

Thanks.

On Thu, Jan 4, 2018 at 12:43 PM, Jordan Deitch <jwdeitch@gmail.com> wrote:
Hi Mana, 

A starting point would be reading about the batch upsert functionality:

You would do something like:
INSERT INTO table ON CONFLICT update... 

This operation would be atomic. You can also look into deferrable constraints such that you would perform all your insert / update operations in a transaction block and accommodate for the constraints. 

I hope this helps to get you on the right track!

Thanks,
Jordan Deitch



pgsql-general by date:

Previous
From: legrand legrand
Date:
Subject: Re: Bulk Insert/Update Scenario
Next
From: Jordan Deitch
Date:
Subject: Re: Bulk Insert/Update Scenario