On 2 September 2016 at 17:05, Christoph Berg <m...@debian.org> wrote: > Re: Craig Ringer 2016-09-02 > <CAMsr+YFr6Sk=bbu2ycorn7z9fohf0cqx29vk5b49dswq6ek...@mail.gmail.com> >> I thought about that but figured it didn't really matter too much, >> when thinking about examples like >> >> # COPY batch_demo FROM '/root/secret.csv' WITH (FORMAT CSV); >> ERROR: could not open file "/root/secret.csv" for reading: Permission denied >> >> or whatever, where the user doesn't understand why they can't read the >> file given that their local client has permission to do so. >> >> I don't feel strongly about this and think that the error on ENOENT is >> by far the most important, so I'll adjust it per your recommendation. > > Couldn't you just add EACCESS to the check as well?
Yeah, probably. Those are really the only two failures I think it's worth reporting for. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
