| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | 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>, Peter Geoghegan <pg(at)bowt(dot)ie>, 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 16:51:07 |
| Message-ID: | CANP8+jK0+32oc4etmDWtbbsanQ6oY+m24bzW8vz5VnMR5DcPzQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
but of course Robert is correct and everything benefits from further review.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Ford | 2018-01-29 16:55:59 | Re: Add RANGE with values and exclusions clauses to the Window Functions |
| Previous Message | Tom Lane | 2018-01-29 16:50:02 | Re: [HACKERS] MERGE SQL Statement for PG11 |