Re: BUG #19388: Failing to connect to postgres with EACCES error - Mailing list pgsql-bugs

From Jacob Champion
Subject Re: BUG #19388: Failing to connect to postgres with EACCES error
Date
Msg-id CAOYmi+ki-_iH6-r-JzXQGur8Jt-iefMhKPhFZWWatrqt0RpFBg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #19388: Failing to connect to postgres with EACCES error  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #19388: Failing to connect to postgres with EACCES error
List pgsql-bugs
On Fri, Jan 23, 2026 at 7:35 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> If anything, I'd lean towards removing the special exception for
> ENOTDIR ... I wonder why that's there.

I think removing that would take some adjustments to
pqGetHomeDirectory(), so that it actually checks for the existence of
that directory before returning true. `have_homedir` is kind of a
misleading name in this context.

--Jacob



pgsql-bugs by date:

Previous
From: surya poondla
Date:
Subject: Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
Next
From: Tom Lane
Date:
Subject: Re: BUG #19388: Failing to connect to postgres with EACCES error