From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
---|---|
To: | surafel3000(at)gmail(dot)com |
Cc: | cmt(at)burggraben(dot)net, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: COPY FROM WHEN condition |
Date: | 2018-10-11 09:12:48 |
Message-ID: | CADkLM=dmvGSpZ+h_CzFoGeuzH7mZT3TLttx-ikc+UYw_e6L2jg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Oct 11, 2018 at 5:04 AM Surafel Temesgen <surafel3000(at)gmail(dot)com>
wrote:
>
>
> On Thu, Oct 11, 2018 at 12:00 PM Christoph Moench-Tegeder <
> cmt(at)burggraben(dot)net> wrote:
>
>> You can:
>> COPY ( query ) TO 'filename';
>>
> it is for COPY FROM
>
> regards
> Surafel
>
It didn't get far, but you may want to take a look at a rejected patch for
copy_srf() (set returning function)
https://www.postgresql.org/message-id/CADkLM%3DdoeiWQX4AGtDNG4PsWfSXz3ai7kY%3DPZm3sUhsUeev9Bg%40mail.gmail.com
https://commitfest.postgresql.org/12/869/
Having a set returning function gives you the full expressiveness of SQL,
at the cost of an extra materialization step.
From | Date | Subject | |
---|---|---|---|
Next Message | Konstantin Knizhnik | 2018-10-11 10:04:48 | Few remarks on JIT , parallel query execution and columnar store... |
Previous Message | Michael Paquier | 2018-10-11 09:06:11 | Re: out-of-order XID insertion in KnownAssignedXids |