Re: abstract Unix-domain sockets
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-11-23T13:50:41Z
Lists: pgsql-hackers
On 2020-11-20 18:23, David G. Johnston wrote: > If there is dead code there is an underlying problem to > address/discover, not just removing the dead code. In this case are we > saying that a new server won’t ever fail to start because the socket > file exists but instead will just clobber the file with its own? Yes. (In practice, there will be an error with respect to the lock file before you even get to that question, but that is different code elsewhere.) > Because given that error, and a server process that failed to clean up > after itself, the correction to take would indeed seem to be to manually > remove the file as the hint says. IOW, fix the code, not the message? I don't understand that. -- Peter Eisentraut 2ndQuadrant, an EDB company https://www.2ndquadrant.com/
Commits
-
Add support for abstract Unix-domain sockets
- c9f0624bc2f5 14.0 landed
-
Make error hint from bind() failure more accurate
- d5d91acdccae 14.0 landed
-
Remove obsolete ifdefs
- 555eb1a4f011 14.0 landed