Re: BUG #19388: Failing to connect to postgres with EACCES error

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: gc(dot)nugent66(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19388: Failing to connect to postgres with EACCES error
Date: 2026-01-23 20:01:18
Message-ID: CAOYmi+ki-_iH6-r-JzXQGur8Jt-iefMhKPhFZWWatrqt0RpFBg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jan 23, 2026 at 7:35 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2026-01-23 20:31:48 Re: BUG #19388: Failing to connect to postgres with EACCES error
Previous Message surya poondla 2026-01-23 18:22:38 Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work