| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: INSERT...ON DUPLICATE KEY IGNORE |
| Date: | 2013-09-03 09:48:18 |
| Message-ID: | CAM3SWZSAjMqtAd6mBBWBcmxNKQt8350EQ4V38kMm9Q9ozvmEpA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 3, 2013 at 2:11 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> and it would be totally unacceptable if that meant that lots of people
> blocked on the page lock that an upserter held while it tried to
> acquire locks on tuples
By which I mean: it seems shaky that I'd then be assuming that to lock
all of a row's unique index values was to lock the row itself, and so
that there was no need to worry about blocking on acquiring an actual
row lock while holding all those exclusive/write buffer locks.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-09-03 12:19:35 | Re: [9.4] Make full_page_writes only settable on server start? |
| Previous Message | Peter Geoghegan | 2013-09-03 09:11:43 | Re: INSERT...ON DUPLICATE KEY IGNORE |