pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: elein <elein@varlena.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Adding MERGE to the TODO list (resend with subject)
Date: Sun, 09 May 2004 13:32:58 +0800
Message-ID: <409DC28A.7010509@familyhealth.com.au> (raw)
In-Reply-To: <20040509051825.GB917@dcc.uchile.cl>
References: <200405082246.i48MkTQ29755@candle.pha.pa.us>
	<409D8E48.3070805@familyhealth.com.au>
	<20040509035405.GA917@dcc.uchile.cl>
	<409DAFEB.7020300@familyhealth.com.au>
	<20040509051825.GB917@dcc.uchile.cl>

>>Except you can keep trying and trying without the outermost transaction 
>>failing.
> 
> But that won't provide the necessary next key locking you mentioned in
> your first email, will it?

No, but since I can loop an infinite number of times until either the 
update or insert works, I don't need next key locking.

BTW, the reference in MySQL:

http://dev.mysql.com/doc/mysql/en/REPLACE.html

Hmm...no refernce to next key locking. Maybe that's an Innodb thing...

Anyway, you can see how they've implemented their algorithm.

Here is docs on the DB2 merge command from which the standard was derived:

http://databasejournal.com/features/db2/article.php/10896_3322041_2

Chris

view thread (16+ messages)  latest in thread

Message-ID: <409DC28A.7010509@familyhealth.com.au>
Permalink:  ../409DC28A.7010509@familyhealth.com.au/
Also on:    postgresql.org/message-id/409DC28A.7010509@familyhealth.com.au

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: chriskl@familyhealth.com.au, alvherre@dcc.uchile.cl, pgman@candle.pha.pa.us, elein@varlena.com, pgsql-hackers@postgresql.org
  Subject: Re: Adding MERGE to the TODO list (resend with subject)
  In-Reply-To: <409DC28A.7010509@familyhealth.com.au>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox