Re: Let file_fdw access COPY FROM PROGRAM
| От | Craig Ringer |
|---|---|
| Тема | Re: Let file_fdw access COPY FROM PROGRAM |
| Дата | |
| Msg-id | CAMsr+YFo3sO3i1dAB+5-nD2AgJP6L8yMAGFeF9nh163cTSzBQw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Let file_fdw access COPY FROM PROGRAM (Corey Huinker <corey.huinker@gmail.com>) |
| Ответы |
Re: Let file_fdw access COPY FROM PROGRAM
|
| Список | pgsql-hackers |
On 3 June 2016 at 04:48, Corey Huinker <corey.huinker@gmail.com> wrote:
A while back, there was a push to make COPY gzip-aware. That didn't happen, but COPY FROM PROGRAM did, and it scratches the same itch.
- writing unwanted columns to a temp/work table via COPY, and then immediately re-reading them
Without wanting to take away from the value of letting file FDW access FROM PROGRAM, I think this really merits a solution that applies to COPY as well. Variants on "how do I COPY just some columns from a CSV" is a real FAQ, and it doesn't seem like it'd be excessively hard to support. We'd just need some way to pass a list of column-ordinals or header-names.
Not asking you to do that work, just pointing out that this particular issue applies to COPY its self as well.
В списке pgsql-hackers по дате отправления: