From: Tom Lane <tgl@sss.pgh.pa.us>
To: richard coleman <rcoleman.ascentgl@gmail.com>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: COPY FROM appears broken in PostgreSQL 15
In-reply-to: 
 <CAGA3vBvJx=YX3SCg4D6oct1RNjqW4ToEXe7=V285gqTQc7x0Fg@mail.gmail.com>
References: 
 <CAGA3vBvJx=YX3SCg4D6oct1RNjqW4ToEXe7=V285gqTQc7x0Fg@mail.gmail.com>
Comments: In-reply-to richard coleman <rcoleman.ascentgl@gmail.com>
	message dated "Tue, 31 Oct 2023 17:08:50 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2637136.1698786704.1@sss.pgh.pa.us>
Date: Tue, 31 Oct 2023 17:11:44 -0400
Message-ID: <2637137.1698786704@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2637137.1698786704%40sss.pgh.pa.us>
Precedence: bulk

richard coleman <rcoleman.ascentgl@gmail.com> writes:
> Did something happen to the COPY FROM command in PostgreSQL 15?

It seems quite unlikely that you'd be the first to notice such
a fundamental problem.

> ERROR:  could not open file "/{path}/{file}" for reading: Permission denied
> HINT:  COPY FROM instructs the PostgreSQL server process to read a file.
> You may want a client-side facility such as psql's \copy.

> I have checked and the postgres user can read/write to the file just fine.

Check that again.  Check lookup permission on all the directories in
the path, too.

			regards, tom lane