aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-11-29 19:57:01 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2012-11-29 19:57:01 -0500
commit4af446e7cd0b37bb5d7fa9b73193c68e14239499 (patch)
tree8e425b0fb24a72ca388b5ae4cbb73c1d655a5bd7 /doc/src
parentd3fe59939c142f2adad2a9cca03e0e0d27c162a4 (diff)
downloadpostgresql-4af446e7cd0b37bb5d7fa9b73193c68e14239499.tar.gz
postgresql-4af446e7cd0b37bb5d7fa9b73193c68e14239499.zip
Produce a more useful error message for over-length Unix socket paths.
The length of a socket path name is constrained by the size of struct sockaddr_un, and there's not a lot we can do about it since that is a kernel API. However, it would be a good thing if we produced an intelligible error message when the user specifies a socket path that's too long --- and getaddrinfo's standard API is too impoverished to do this in the natural way. So insert explicit tests at the places where we construct a socket path name. Now you'll get an error that makes sense and even tells you what the limit is, rather than something generic like "Non-recoverable failure in name resolution". Per trouble report from Jeremy Drake and a fix idea from Andrew Dunstan.
Diffstat (limited to 'doc/src')
0 files changed, 0 insertions, 0 deletions