mirror of https://github.com/postgres/postgres
only possible failure is in pq_flush, which will log a (better!) report anyway --- so pq_endmessage is just cluttering the log with a redundant entry. This matters when a client crashes partway through a large query, since we will emit many broken-pipe reports before finishing the query and exiting.REL7_1_STABLE
parent
c8e05affe4
commit
6ccb2af725
Loading…
Reference in new issue