>> I'd move the comma not remove it; and I think "the pg_read_file()" is
>> pretty bad English too. So perhaps
>>
>> Note that granting users the EXECUTE privilege on
>> pg_read_file(), or related functions, allows them
>> the
>> ability to read any file on the server which the
>> It seems there's an extra comma between "related" and "functions". Am I
>> correct?
>
> I'd move the comma not remove it; and I think "the pg_read_file()" is
> pretty bad English too. So perhaps
>
> Note that granting users the EXECUTE privilege on
> pg_read_file(), or related
David Fetter writes:
> Is there a useful distinction to be drawn between the files readable
> by the system user who owns the database and those the database itself
> can read?
Probably not. It's possible to create such a distinction with SELinux
or other security tools, but not in plain Unix,
On Tue, Dec 18, 2018 at 06:16:14PM -0500, Tom Lane wrote:
> Tatsuo Ishii writes:
> > While translating the manual into Japanese, I had a hard time to
> > parse following sentence in func.sgml:
>
> > Note that granting users the EXECUTE privilege on the
> > pg_read_file(), or related,
Tatsuo Ishii writes:
> While translating the manual into Japanese, I had a hard time to
> parse following sentence in func.sgml:
> Note that granting users the EXECUTE privilege on the
> pg_read_file(), or related, functions allows them the
> ability to read any file on the server
