| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Shay Rojansky <roji(at)roji(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Haumacher, Bernhard" <haui(at)haumacher(dot)de>, Dave Cramer <davecramer(at)postgres(dot)rocks> |
| Subject: | Re: Error on failed COMMIT |
| Date: | 2020-02-23 12:14:25 |
| Message-ID: | CAB=Je-GW5Ed-YiPV0w1uNRXFET-AGd00pSBeam6hPWC_uP_8VQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Shay> Asking drivers to do this at the client have the exact same breakage
impact as the server change, since the user-visible behavior changes in the
same way
+1
Dave>While we can certainly code around this in the client drivers I don't
believe they should be responsible for fixing the failings of the server.
Application developers expect that the database feels the same no matter
which driver is used, so it would be better to avoid a case
when half of the drivers create exceptions on non-committing-commit, and
another half silently loses data.
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2020-02-23 17:24:00 | Ought binary literals to allow spaces? |
| Previous Message | Dave Cramer | 2020-02-23 11:16:23 | Re: Error on failed COMMIT |