forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit69fed5b
committed
Ensure libpq reports a suitable error message on unexpected socket EOF.
The EOF-detection logic in pqReadData was a bit confused about who shouldset up the error message in case the kernel gives us read-ready-but-no-datarather than ECONNRESET or some other explicit error condition. Since thewhole point of this situation is that the lower-level functions don't knowthere's anything wrong, pqReadData itself must set up the message. Butkeep the assumption that if an errno was reported, a message was set up atlower levels.Per bug #11712 from Marko Tiikkaja. It's been like this for a very longtime, so back-patch to all supported branches.1 parent2ae7811 commit69fed5b
1 file changed
+11
-8
lines changedLines changed: 11 additions & 8 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
764 | 764 |
| |
765 | 765 |
| |
766 | 766 |
| |
767 |
| - | |
768 |
| - | |
769 |
| - | |
770 |
| - | |
771 |
| - | |
772 |
| - | |
| 767 | + | |
| 768 | + | |
773 | 769 |
| |
774 | 770 |
| |
775 | 771 |
| |
| |||
808 | 804 |
| |
809 | 805 |
| |
810 | 806 |
| |
811 |
| - | |
812 |
| - | |
| 807 | + | |
813 | 808 |
| |
| 809 | + | |
| 810 | + | |
| 811 | + | |
| 812 | + | |
| 813 | + | |
| 814 | + | |
| 815 | + | |
| 816 | + | |
814 | 817 |
| |
815 | 818 |
| |
816 | 819 |
| |
|
0 commit comments
Comments
(0)