Re: parse_slash_copy doesn't support psql variables substitution

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: parse_slash_copy doesn't support psql variables substitution
Date: 2021-02-11 23:36:49
Message-ID: CADkLM=ds+h8YtZh31nF5Pj8Y=Ak7SxQsdgSVrgUbO0b5yo74Dg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 10, 2021 at 8:33 AM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-02-11 23:42:04 Re: WIP: WAL prefetch (another approach)
Previous Message Ranier Vilela 2021-02-11 22:55:45 Re: pg_cryptohash_final possible out-of-bounds access (per Coverity)