| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication protocol doc fix |
| Date: | 2021-07-31 00:09:56 |
| Message-ID: | 20210731000956.oropiwiwblg6l7jw@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2021-06-17 16:37:51 -0700, Jeff Davis wrote:
> In theory, it could break a client that issues Parse+Bind+Execute for a
> CopyIn/CopyBoth command without a Sync, but I'm not sure there are any
> clients that do that, and it's arguable whether the documentation
> permitted that or not anyway.
I'm worried about that breaking things and us only noticing down the
road. This doesn't fix a problem that we are actively hitting, and as
you say it's arguably compliant to do it differently. Potential protocol
incompatibilities are a dangerous area. I think before doing something
like this we ought to at least verify that the most popular native
drivers won't have a problem with the change. Maybe pgjdbc, npgsql, the
popular go ones and rust-postgres?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2021-07-31 00:42:47 | Re: Asynchronous and "direct" IO support for PostgreSQL. |
| Previous Message | Alvaro Herrera | 2021-07-30 23:51:39 | Re: archive status ".ready" files may be created too early |