aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistsplit.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-02-20 15:02:41 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2022-02-20 15:02:41 -0500
commit83a7637e2c5be27a0788b920501dde284b3fca33 (patch)
tree87a1c7feee188c06bfc74648ae26405b2e293270 /src/backend/access/gist/gistsplit.c
parent1c6d4629394d1b696b4e47ab4c501752e8c974e7 (diff)
downloadpostgresql-83a7637e2c5be27a0788b920501dde284b3fca33.tar.gz
postgresql-83a7637e2c5be27a0788b920501dde284b3fca33.zip
Reset conn->errorReported when PQrequestCancel sets errorMessage.
Oversight in commit 618c16707. This is mainly neatnik-ism, since if PQrequestCancel is used per its API contract, we should perform pqClearConnErrorState before reaching any place that would consult errorReported. But still, it seems like a bad idea to potentially leave errorReported pointing past errorMessage.len.
Diffstat (limited to 'src/backend/access/gist/gistsplit.c')
0 files changed, 0 insertions, 0 deletions