| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Rudolf Gavlas <r(dot)stu3(dot)1(at)googlemail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH] get_home_path: use HOME |
| Date: | 2016-09-21 15:20:10 |
| Message-ID: | 0430af0b-d7ed-c78c-4ea8-2ba7a759932e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/20/16 1:44 PM, Rudolf Gavlas wrote:
> If you think that using the value of HOME variable as the user's home
> directory is bad idea, I won't argue with that, I've already expressed
> my opinion. What is the real problem here is using home directory of a
> user A as a home directory for user B. That's clearly a bug and if you
> want to solve it without using HOME, I am fine with that.
I have no problem with using the HOME variable optionally. That is
wide-spread practice. But I dispute what you describe as the "real
problem". In Unix, users are identified by uids. The real problem, as
I see it, is that you think you have multiple users but you actually don't.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2016-09-21 15:25:14 | Re: New SQL counter statistics view (pg_stat_sql) |
| Previous Message | Peter Eisentraut | 2016-09-21 15:03:45 | wal_segment size vs max_wal_size |