Re: abstract Unix-domain sockets - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: abstract Unix-domain sockets
Date
Msg-id 5d2dc07b-1495-ae79-9034-8f45e7e7ca80@2ndquadrant.com
Whole thread Raw
In response to Re: abstract Unix-domain sockets  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: abstract Unix-domain sockets  ("David G. Johnston" <david.g.johnston@gmail.com>)
List 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/



pgsql-hackers by date:

Previous
From: Daniil Zakhlystov
Date:
Subject: Re: libpq compression
Next
From: Tomas Vondra
Date:
Subject: Re: [PoC] Non-volatile WAL buffer