Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    The EOF-detection logic in pqReadData was a bit confused about who should
    set up the error message in case the kernel gives us read-ready-but-no-data
    rather than ECONNRESET or some other explicit error condition.  Since the
    whole point of this situation is that the lower-level functions don't know
    there's anything wrong, pqReadData itself must set up the message.  But
    keep the assumption that if an errno was reported, a message was set up at
    lower levels.
    
    Per bug #11712 from Marko Tiikkaja.  It's been like this for a very long
    time, so back-patch to all supported branches.
    69fed5b2
    History
    Name Last commit Last update