| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade permission check |
| Date: | 2011-05-16 15:57:38 |
| Message-ID: | 201105161557.p4GFvck25655@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I have added the attached patch to pg_upgrade to print a clear error
> > message if you don't have read/write/execute permission in the current
> > directory, which is needed for pg_upgrade to read/write temporary files.
>
> "full access permissions" seems unhelpfully vague. Why not say
> "you must have both read and write access to the current directory"?
OK, I can do that, but they need execute permission in that directory
too to look up file names in there. Should I say execute too?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-05-16 16:10:35 | Re: pg_upgrade permission check |
| Previous Message | Tom Lane | 2011-05-16 15:48:14 | Re: pg_upgrade permission check |