| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] MERGE SQL Statement for PG11 |
| Date: | 2018-01-29 17:35:15 |
| Message-ID: | CAH2-Wz=-KCTK0D_NDHouYsfTWe=tK1n8pa0eKf2Q7bub3xFnAw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 29, 2018 at 8:51 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 29 January 2018 at 16:44, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
>> I think the question is how does it handle cases it doesn't support?
>> Does it give wrong answers? Does it give a helpful error message? Can
>> you summarize that?
>
> I'm happy to report that it gives correct answers to every known MERGE
> test, except
>
> * where it hits a concurrency issue and throws SQLCODE =
> ERRCODE_T_R_SERIALIZATION_FAILURE and the standard text for that
>
> * where it hits an unsupported feature and throws SQLCODE =
> ERRCODE_FEATURE_NOT_SUPPORTED, with appropriate text
What specific features does it not work with already? A list would be helpful.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2018-01-29 18:14:39 | Re: [HACKERS] MERGE SQL Statement for PG11 |
| Previous Message | Peter Geoghegan | 2018-01-29 17:23:58 | Re: [HACKERS] MERGE SQL Statement for PG11 |