On Mon, Jan 29, 2018 at 8:51 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On 29 January 2018 at 16:44, Bruce Momjian <bruce@momjian.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