Re: INSERT...ON DUPLICATE KEY IGNORE

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: INSERT...ON DUPLICATE KEY IGNORE
Date: 2013-09-05 16:52:20
Message-ID: CA+TgmoYqPiL1JJk=Bh6JthidDqOrHJRza+v7+bid4thQ26Npjw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 4, 2013 at 8:08 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> You've proposed an framework and algorithm for something I'd really, really like to see. I don't think that it can work explicitly as you proposed, so I roughly sketched out a solution I can see.
> I don't want "my" idea to win, I want a idea to win. I haven't fleshed out my idea to the point where I would consider it something ready to implement or something.
> You're the patch author here whose plans are laid open to be scrutinized ;). If you think my idea has merit, use and adapt it to reality. If not, find another, better, solution.
>
> Even if our path to that goal is confrontational at times, the goal is to find a good solution, not the argument itself.

Totally agreed.

> I haven't argued about INSERT ... DUPLICATE LOCK because the page locking scheme doesn't seem to work out for plain DUPLICATE. No need to think/argue about the fancier version in that case.

Check.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2013-09-05 16:53:18 Re: get rid of SQL_ASCII?
Previous Message Tom Lane 2013-09-05 16:48:54 Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers