Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution(exec.c) - Mailing list pgsql-bugs

From Christoph Berg
Subject Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution(exec.c)
Date
Msg-id 20180317204051.GG23570@msg.df7cb.de
Whole thread Raw
In response to Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c)  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Responses Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c)  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution(exec.c)  (Petar Bogdanovic <petar@smokva.net>)
List pgsql-bugs
Re: Andrew Gierth 2018-03-17 <87in9uhbco.fsf@news-spur.riddles.org.uk>
>  Tom> I think your example of "sudo /usr/bin/pg_ctl" is pretty
>  Tom> artificial; who'd bother spelling that out?
> 
> Not necessarily exactly like that, but we do occasionally get this issue
> coming up on the IRC channel.

It's absolutely not artificial. I can easily trigger the message from
my home directory:

$ chmod 700 .
$ sudo -u postgres psql
could not change directory to "/home/cbe": Permission denied

I never observed any negative side effects of it, though. (Except for
the obvious fact that "\i somethinginmyhome.sql" won't work.)

Christoph


pgsql-bugs by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c)
Next
From: Tom Lane
Date:
Subject: Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c)