Re: MERGE vs REPLACE - Mailing list pgsql-hackers

From Tom Lane
Subject Re: MERGE vs REPLACE
Date
Msg-id 22373.1131751078@sss.pgh.pa.us
Whole thread Raw
In response to Re: MERGE vs REPLACE  (Josh Berkus <josh@agliodbs.com>)
Responses Re: MERGE vs REPLACE  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> But even REPLACE requires predicate locking.  There's no real way to get 
> around it.

The point though is that REPLACE is restricted to a type of predicate
narrow enough to be enforced through a unique-index mechanism, and so
it's implementable without solving the general case of predicate
locking.

Predicate locking for narrow cases isn't very hard; it's the general
case of arbitrary predicates that's hard.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: MERGE vs REPLACE
Next
From: Gavin Sherry
Date:
Subject: Re: MERGE vs REPLACE