| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Subject: | Re: UPSERT wiki page, and SQL MERGE syntax |
| Date: | 2014-10-02 07:07:45 |
| Message-ID: | 542CF9C1.3000704@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/02/2014 02:52 AM, Peter Geoghegan wrote:
> Having been surprisingly successful at advancing our understanding of
> arguments for and against various approaches to "value locking", I
> decided to try the same thing out elsewhere. I have created a
> general-purpose UPSERT wiki page.
>
> The page is: https://wiki.postgresql.org/wiki/UPSERT
Thanks!
Could you write down all of the discussed syntaxes, using a similar
notation we use in the manual, with examples on how to use them? And
some examples on what is possible with some syntaxes, and not with
others? That would make it a lot easier to compare them.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-10-02 07:11:21 | Re: bad estimation together with large work_mem generates terrible slow hash joins |
| Previous Message | Etsuro Fujita | 2014-10-02 06:55:30 | Typo fixes in src/backend/rewrite/rewriteHandler.c |