Re: parse_slash_copy doesn't support psql variables substitution - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: parse_slash_copy doesn't support psql variables substitution
Date
Msg-id CADkLM=ds+h8YtZh31nF5Pj8Y=Ak7SxQsdgSVrgUbO0b5yo74Dg@mail.gmail.com
Whole thread Raw
In response to parse_slash_copy doesn't support psql variables substitution  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Wed, Feb 10, 2021 at 8:33 AM Pavel Stehule <pavel.stehule@gmail.com> wrote:
Hi

Is there some reason why \copy statement (parse_slash_copy parser) doesn't support psql variables?

Regards

Pavel

I remember wondering about that when I was working on the \if stuff. I dug into it a bit, but the problem was out of scope for my goals.

The additional options recently added to \g reduced my need for \copy, and it seemed liked there was some effort to have input pipes as well, that would eliminate the need for \copy altogether.

 

pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: pg_cryptohash_final possible out-of-bounds access (per Coverity)
Next
From: Tomas Vondra
Date:
Subject: Re: WIP: WAL prefetch (another approach)