| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Dave Cramer <davecramer(at)postgres(dot)rocks>, Shay Rojansky <roji(at)roji(dot)org>, "Haumacher, Bernhard" <haui(at)haumacher(dot)de>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Subject: | Re: Error on failed COMMIT |
| Date: | 2020-02-27 04:04:34 |
| Message-ID: | CA+TgmoY7EJ1=ooTzg7_7QyPkvmdfgw446CzV8Kg7WfH4FKNxOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 26, 2020 at 11:53 PM Vladimir Sitnikov
<sitnikov(dot)vladimir(at)gmail(dot)com> wrote:
> Pushing full SQL parser to the driver is not the best idea taking into the account the extensibility the core has.
That wouldn't be necessary. You could just do strcmp() on the command tag.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Sitnikov | 2020-02-27 04:11:26 | Re: Error on failed COMMIT |
| Previous Message | Robert Haas | 2020-02-27 04:03:15 | Re: allow frontend use of the backend's core hashing functions |