diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-11-29 19:57:33 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-11-29 19:57:33 -0500 |
commit | 25b2499d56ab62ae80dc39dd09e80542d7967a2e (patch) | |
tree | 0008373a5e65fb52e4e3aaa4ad85eed8ab45ca42 /contrib/btree_gist/sql/numeric.sql | |
parent | 518d58daa579a3b1de6d7ef2a3fc81b75f80fc1a (diff) |
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 'contrib/btree_gist/sql/numeric.sql')
0 files changed, 0 insertions, 0 deletions