Skip site navigation (1) Skip section navigation (2)

Re: Data Warehouse Reevaluation - MySQL vs Postgres --

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Markus Schaber <schabios(at)logi-track(dot)com>
Cc: PostgreSQL Performance List <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Data Warehouse Reevaluation - MySQL vs Postgres --
Date: 2004-09-14 14:33:03
Message-ID: 20040914143303.GR21419@ns.snowman.net (view raw or flat)
Thread:
Lists: pgsql-performance
* Markus Schaber (schabios(at)logi-track(dot)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.

Otherwise, what I've done is basically an update followed by an insert
using outer joins.  If there's something better, I'd love to hear about
it.  The statements looks something like:

update X
  set colA = a.colA,
      colB = a.colB
  from Y a
  where keyA = a.keyA and
        keyB = a.keyB;

insert into X
  select a.keyA,
         a.keyB,
	 a.colA,
	 a.colB
  from Y a left join X b
       using (keyA, keyB)
  where b.keyA is NULL and
        b.keyB is NULL;

With the appropriate indexes, this is pretty fast but I think a merge
would be much faster.

		Thanks,

			Stephen

In response to

Responses

pgsql-performance by date

Next:From: Harald Lau (Sector-X)Date: 2004-09-14 15:20:43
Subject: Re: Data Warehouse Reevaluation - MySQL vs Postgres -- merge tables
Previous:From: Michael KleiserDate: 2004-09-14 14:23:02
Subject: Re: Data Warehouse Reevaluation - MySQL vs Postgres --

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group