summaryrefslogtreecommitdiff
path: root/src/backend/storage/ipc/shmqueue.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-11-29 19:57:24 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2012-11-29 19:57:24 -0500
commit31c341ae13eb8adbc0007baa303efd84c2735fbe (patch)
treecac9ddf6314d2735f291bf60cadb1fd91539ecef /src/backend/storage/ipc/shmqueue.c
parentf4a3e679306ebfbd150d8af3cdd481bea1619c52 (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 'src/backend/storage/ipc/shmqueue.c')
0 files changed, 0 insertions, 0 deletions