pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Alvaro Herrera <alvherre@dcc.uchile.cl>
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, 9 May 2004 23:58:12 -0400 (EDT)
Message-ID: <200405100358.i4A3wCp02854@candle.pha.pa.us> (raw)
In-Reply-To: <409DC28A.7010509@familyhealth.com.au>


Added to TODO:

	* Add MERGE command that does UPDATE, or on failure, INSERT


---------------------------------------------------------------------------

Christopher Kings-Lynne wrote:
> >>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
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (16+ messages)  latest in thread

Message-ID: <200405100358.i4A3wCp02854@candle.pha.pa.us>
Permalink:  ../200405100358.i4A3wCp02854@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200405100358.i4A3wCp02854@candle.pha.pa.us

 · 

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: pgman@candle.pha.pa.us, chriskl@familyhealth.com.au, alvherre@dcc.uchile.cl, elein@varlena.com, pgsql-hackers@postgresql.org
  Subject: Re: Adding MERGE to the TODO list (resend with subject)
  In-Reply-To: <200405100358.i4A3wCp02854@candle.pha.pa.us>

* 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