| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, petar(at)smokva(dot)net, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c) |
| Date: | 2018-03-17 20:40:51 |
| Message-ID: | 20180317204051.GG23570@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Re: Andrew Gierth 2018-03-17 <87in9uhbco(dot)fsf(at)news-spur(dot)riddles(dot)org(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-03-17 20:47:16 | Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c) |
| Previous Message | Andrew Gierth | 2018-03-17 19:59:30 | Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c) |