| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Subject: | Re: Promise index tuples for UPSERT |
| Date: | 2014-10-08 13:29:56 |
| Message-ID: | CA+U5nMKER9r4tYABYdqY8O_5y4CHiRNFdmM0tKwq-+pMxDDGHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8 October 2014 00:34, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> INSERTs see #2 win, and by a wider margin than #1 beat #2 with
> UPDATEs. However, insert.sh is by design very unsympathetic towards
> #1. It uses a serial primary key, so every INSERT uselessly obtains a
> HW lock on the same leaf page for the duration of heap insertion.
> Anyway, the median INSERT TPS numbers is 17,759.53 for #1, and
> 20,441.57 TPS for #2. So you're pretty much seeing the full brunt of
> page heavyweight locking, and it isn't all that bad.
Lets see the results of running a COPY please.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-10-08 13:35:33 | Re: Wait free LW_SHARED acquisition - v0.9 |
| Previous Message | Simon Riggs | 2014-10-08 13:25:43 | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} |