Re: Replication protocol doc fix - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Replication protocol doc fix
Date
Msg-id 20210731000956.oropiwiwblg6l7jw@alap3.anarazel.de
Whole thread Raw
In response to Re: Replication protocol doc fix  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Replication protocol doc fix  (Daniel Gustafsson <daniel@yesql.se>)
List 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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: archive status ".ready" files may be created too early
Next
From: Thomas Munro
Date:
Subject: Re: Asynchronous and "direct" IO support for PostgreSQL.