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

Re: UPSERT

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Jonathan Scher" <js(at)oxado(dot)com>
Subject: Re: UPSERT
Date: 2007-03-02 19:17:46
Message-ID: 200703021117.47121.josh@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Couple notes:

(1) Upsert is not just a desire of MySQL users.  I just spec'd a major 
proprietary-database replacement project at a fortune 500 where they want an 
Upsert and are unhappy that PostgreSQL doesn't have it.  Unfortunately, they 
don't want to spring for development funds :-(

(2) Doing upsert by checking for a unique key violaton error leads to horrible 
performance in addition to the previously mentioned race conditions.

-- 
Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

pgsql-hackers by date

Next:From: Andrew - SupernewsDate: 2007-03-02 19:28:44
Subject: Re: GIST and TOAST
Previous:From: David FetterDate: 2007-03-02 19:09:22
Subject: Re: [HACKERS] WITH/RECURSIVE plans

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