Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
From: "Daniel Verite" <daniel@manitou-mail.org>
Subject: Re: variable filename for psql \copy
To: =?UTF-8?Q?Ji=C5=99=C3=AD_Fejfar?= <jurafejfar@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
In-Reply-To: <CA+8wVNX6WgxgUxPFka=Ob-OQhOZVg0XM-NYqwHa5KTFr38JEJw@mail.gmail.com>
Date: Mon, 25 Apr 2022 12:24:47 +0200
Message-Id: <bdbe1e0b-3b20-4781-a0dc-6922563a1a5b@manitou-mail.org>
Archived-At: <https://www.postgresql.org/message-id/bdbe1e0b-3b20-4781-a0dc-6922563a1a5b%40manitou-mail.org>
Precedence: bulk

	Ji=C5=99=C3=AD Fejfar wrote:

> I have found maybe buggy behaviour (of psql parser?) when using psql \copy
> with psql variable used for filename.

While it's annoying that it doesn't work as you tried it, this behavior is=
=20
documented, so in that sense it's not a bug.
The doc also suggests a workaround in a tip section:

=46rom psql manpage:

  The syntax of this command is similar to that of the SQL COPY
   command. All options other than the data source/destination are as
   specified for COPY. Because of this, special parsing rules apply to
   the \copy meta-command. Unlike most other meta-commands, the entire
   remainder of the line is always taken to be the arguments of \copy,
   and neither variable interpolation nor backquote expansion are
   performed in the arguments.

       Tip
       Another way to obtain the same result as \copy ... to is to use
       the SQL COPY ... TO STDOUT command and terminate it with \g
       filename or \g |program. Unlike \copy, this method allows the
       command to span multiple lines; also, variable interpolation
       and backquote expansion can be used.


Best regards,
--=20
Daniel V=C3=A9rit=C3=A9
https://postgresql.verite.pro/
Twitter: @DanielVerite