diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-11-29 19:57:10 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-11-29 19:57:10 -0500 |
commit | a8e60f0b23fa263c9c451cbb6d36f0bc9c196610 (patch) | |
tree | 7b28788981426def8480910d1634be1b96c6de90 /src/backend/executor/nodeHash.c | |
parent | edfc84b878d667bb074048cccb5f363ea66a82c8 (diff) | |
download | postgresql-a8e60f0b23fa263c9c451cbb6d36f0bc9c196610.tar.gz postgresql-a8e60f0b23fa263c9c451cbb6d36f0bc9c196610.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 'src/backend/executor/nodeHash.c')
0 files changed, 0 insertions, 0 deletions