Re: MERGE vs REPLACE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: josh(at)agliodbs(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org, Jaime Casanova <systemguards(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: MERGE vs REPLACE
Date: 2005-11-11 23:17:58
Message-ID: 22373.1131751078@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Sherry 2005-11-11 23:23:56 Re: MERGE vs REPLACE
Previous Message Rod Taylor 2005-11-11 23:00:32 Re: MERGE vs REPLACE