COPY TO returns "ERROR: could not open file for writing: No such file or directory" - Mailing list pgsql-general

From David Noel
Subject COPY TO returns "ERROR: could not open file for writing: No such file or directory"
Date
Msg-id CAHAXwYDhwxsb9iP9sA0r68R8dHb1iugT7c=wi82wCAqamXaLQw@mail.gmail.com
Whole thread Raw
Responses Re: COPY TO returns "ERROR: could not open file for writing: No such file or directory"  (Alban Hertroys <haramrae@gmail.com>)
Re: COPY TO returns "ERROR: could not open file for writing: No such file or directory"  (David G Johnston <david.g.johnston@gmail.com>)
List pgsql-general
COPY (SELECT * FROM page WHERE "PublishDate" between '2014-03-01' and
'2014-04-01') TO
'/home/ygg/sql/backup/pagedump.2014-03-01.to.2014-04-01.copy';

gives me:

ERROR:  could not open file
"/home/ygg/sql/backup/pagedump.2014-03-01.to.2014-04-01.copy" for
writing: No such file or directory

Running it in pgadmin3 I get the additional output:

SQL state: 58P01

I've tried creating a file named
"pagedump.2014-03-01.to.2014-04-01.copy", changing its permissions,
and changing its owner to pgsql, all with no luck.

The syntax for COPY is:

COPY { table_name [ ( column_name [, ...] ) ] | ( query ) }
    TO { 'filename' | PROGRAM 'command' | STDOUT }
    [ [ WITH ] ( option [, ...] ) ]

...so it *should* be running just fine. I can't figure out why it's not.

FreeBSD. PostgreSQL 9.3.

Has anyone run into this before?


pgsql-general by date:

Previous
From: Chris Ernst
Date:
Subject: Re: Downtime-free 'alter table set tablespace'
Next
From: Alban Hertroys
Date:
Subject: Re: COPY TO returns "ERROR: could not open file for writing: No such file or directory"