mirror of https://github.com/postgres/postgres
The original coding did this in pqDropServerData(), which seems fairly backwards. Pending commands are more like already-queued output data, which is dropped in pqDropConnection(). Moving the operation means that we clear the command queue immediately upon detecting connection drop, which improves the sanity of subsequent behavior. In particular this eliminates duplicated error message text as a consequence of code added inpull/83/headb15f25446
, which supposed that a nonempty command queue must mean the prior operation is still active. There might be an argument for backpatching this to v14; but as withb15f25446
, I'm unsure about interactions with618c16707
. For now, given the lack of complaints about v14's behavior, leave it alone. Per report from Peter Eisentraut. Discussion: https://postgr.es/m/de57761c-b99b-3435-b0a6-474c72b1149a@enterprisedb.com
parent
b5f44225b8
commit
93909599cd
Loading…
Reference in new issue