Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> "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
Bruce Momjian writes:
> Tom Lane wrote:
>> "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
Tom Lane wrote:
> Bruce Momjian 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" se
Bruce Momjian 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
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.
This is based on a bug report I received from EnterpriseDB usage
testing.
--
Bruc
