Re: UPSERT - Mailing list pgsql-hackers

From Tom Lane
Subject Re: UPSERT
Date
Msg-id 6261.1172848398@sss.pgh.pa.us
Whole thread Raw
In response to Re: UPSERT  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: UPSERT
Re: UPSERT
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> My instinct would be to follow your first strategy, i.e. detect which 
> path is needed rather than try one and then if it fails do the other.

The very first thing you need to think about is how to solve the race
condition problem, ie, two backends concurrently trying to insert
identical data.  Until you have a plausible mechanism for that, the
whole thing is pie-in-the-sky.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: HOT - whats next ?
Next
From: "Pavan Deolasee"
Date:
Subject: Re: HOT - whats next ?