MIME-Version: 1.0
From: Dean Rasheed <dean.a.rasheed@gmail.com>
Date: Mon, 20 Feb 2023 19:49:56 +0000
Message-ID: <CAEZATCUMe+_KedPMM9AxKqm=SZogSxjUcrMe+sakusZh3BFcQw@mail.gmail.com>
Subject: Allow MERGE to be executed from PL/Tcl
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: multipart/mixed; boundary="00000000000053beea05f526f855"
Archived-At: <https://www.postgresql.org/message-id/CAEZATCUMe%2B_KedPMM9AxKqm%3DSZogSxjUcrMe%2BsakusZh3BFcQw%40mail.gmail.com>
Precedence: bulk

--00000000000053beea05f526f855
Content-Type: text/plain; charset="UTF-8"

Another one noticed in the MERGE RETURNING patch -- this allows PL/Tcl
to execute MERGE (i.e., don't fail when SPI returns SPI_OK_MERGE). I'm
not sure if anyone uses PL/Tcl anymore, but it's a trivial fix,
probably not worth a regression test case.

Regards,
Dean

--00000000000053beea05f526f855
Content-Type: application/x-patch; name="allow-merge-in-pltcl.patch"
Content-Disposition: attachment; filename="allow-merge-in-pltcl.patch"
Content-Transfer-Encoding: base64
Content-ID: <f_led79gur0>
X-Attachment-Id: f_led79gur0

ZGlmZiAtLWdpdCBhL3NyYy9wbC90Y2wvcGx0Y2wuYyBiL3NyYy9wbC90Y2wvcGx0Y2wuYwpuZXcg
ZmlsZSBtb2RlIDEwMDY0NAppbmRleCAxODVkNWJlLi40OTlhOWVhCi0tLSBhL3NyYy9wbC90Y2wv
cGx0Y2wuYworKysgYi9zcmMvcGwvdGNsL3BsdGNsLmMKQEAgLTI0NDEsNiArMjQ0MSw3IEBAIHBs
dGNsX3Byb2Nlc3NfU1BJX3Jlc3VsdChUY2xfSW50ZXJwICppbnQKIAkJY2FzZSBTUElfT0tfSU5T
RVJUOgogCQljYXNlIFNQSV9PS19ERUxFVEU6CiAJCWNhc2UgU1BJX09LX1VQREFURToKKwkJY2Fz
ZSBTUElfT0tfTUVSR0U6CiAJCQlUY2xfU2V0T2JqUmVzdWx0KGludGVycCwgVGNsX05ld1dpZGVJ
bnRPYmoobnR1cGxlcykpOwogCQkJYnJlYWs7CiAK
--00000000000053beea05f526f855--