forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit9814437
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 parentd5fef87 commit9814437
1 file changed
+11
-8
lines changedLines changed: 11 additions & 8 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
738 | 738 |
| |
739 | 739 |
| |
740 | 740 |
| |
741 |
| - | |
742 |
| - | |
743 |
| - | |
744 |
| - | |
745 |
| - | |
746 |
| - | |
| 741 | + | |
| 742 | + | |
747 | 743 |
| |
748 | 744 |
| |
749 | 745 |
| |
| |||
782 | 778 |
| |
783 | 779 |
| |
784 | 780 |
| |
785 |
| - | |
786 |
| - | |
| 781 | + | |
787 | 782 |
| |
| 783 | + | |
| 784 | + | |
| 785 | + | |
| 786 | + | |
| 787 | + | |
| 788 | + | |
| 789 | + | |
| 790 | + | |
788 | 791 |
| |
789 | 792 |
| |
790 | 793 |
| |
|
0 commit comments
Comments
(0)