| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Help with 9.5 feature wiki page |
| Date: | 2015-05-21 03:40:14 |
| Message-ID: | CAB7nPqQHZ2JYurJAQ7jLwYXoK6rUPHqcubGJZT74Px5+kGitWA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Thu, May 21, 2015 at 12:07 PM, Peter Geoghegan
<peter(dot)geoghegan86(at)gmail(dot)com> wrote:
> On Wed, May 20, 2015 at 7:52 PM, Peter Geoghegan
> <peter(dot)geoghegan86(at)gmail(dot)com> wrote:
>> Due to some MediaWiki weirdness, I cannot login to edit it.
>
> BTW, I wanted to edit the description of UPSERT. It's not true that
> the use of a CTE can be considered a workaround. That pattern can
> result in a spurious duplicate violation error with concurrent
> upserters, and so I'd definitely discourage it. The only workarounds
> that are robust involve subtransactions, like the plpgsql example in
> the docs, and there is no declarative way to do that. You need to
> catch a duplicate violation and retry to get a robust insert-or-update
> outcome.
Perhaps adding this link from the docs mentioning merge_db() would be
nice (cannot do it myself because of access forbidden with 403 when
attempting to login):
http://www.postgresql.org/docs/9.4/static/plpgsql-control-structures.html
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2015-05-21 05:46:30 | Re: Help with 9.5 feature wiki page |
| Previous Message | Peter Geoghegan | 2015-05-21 03:07:37 | Re: Help with 9.5 feature wiki page |