From: "Simon Riggs" <simon@2ndquadrant.com>
To: "Stephen Frost" <sfrost@snowman.net>,
	"Markus Schaber" <schabios@logi-track.com>
Cc: "PostgreSQL Performance List" <pgsql-performance@postgresql.org>
Subject: Re: Data Warehouse Reevaluation - MySQL vs Postgres --
Date: Tue, 14 Sep 2004 21:38:49 +0100
Message-ID: <NOEFLCFHBPDAFHEIPGBOEEHKCEAA.simon@2ndquadrant.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20040914143303.GR21419@ns.snowman.net>
Importance: Normal

> Stephen Frost
> * Markus Schaber (schabios@logi-track.com) wrote:
> > Generally, what is the fastest way for doing bulk processing of
> > update-if-primary-key-matches-and-insert-otherwise operations?
>
> This is a very good question, and I havn't seen much of an answer to it
> yet.  I'm curious about the answer myself, actually.  In the more recent
> SQL specs, from what I understand, this is essentially what the 'MERGE'
> command is for.  This was recently added and unfortunately is not yet
> supported in Postgres.  Hopefully it will be added soon.
>

Yes, I think it is an important feature for both Data Warehousing (used in
set-operation mode for bulk processing) and OLTP (saves a round-trip to the
database, so faster on single rows also). It's in my top 10 for 2005.

Best Regards, Simon Riggs