From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
---|---|
To: | "Isaac Morland" <isaac(dot)morland(at)gmail(dot)com>, Darafei Komяpa Praliaskouski <me(at)komzpa(dot)net> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "Chapman Flack" <chap(at)anastigmatix(dot)net>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: COPY table_name (single_column) FROM 'unknown.txt' DELIMITER E'\n' |
Date: | 2021-05-06 16:02:30 |
Message-ID: | d63f125e-9bb1-4769-8a49-8cc049477510@www.fastmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, May 6, 2021, at 13:41, Isaac Morland wrote:
> On Thu, 6 May 2021 at 02:21, Darafei "Komяpa" Praliaskouski <me(at)komzpa(dot)net> wrote:
>
>> What I would prefer is some new COPY mode like RAW that will just push whatever it gets on the stdin/input into the cell on the server side. This way it can be proxied by psql, utilize existing infra for passing streams and be used in shell scripting.
>
> Yes! A significant missing feature is “take this arbitrary bucket of bits and move it to/from the database from/to this file without modification of any kind”. There are all sorts of tutorials on the Web about how to almost do it or fake it or convert to hex or whatever but I’ve never seen a nice simple explanation of “here is the command:”.
>
> Of course there is a lot to think about. Coming out of the database, the query result must be exactly one row containing exactly one column; how do we handle other database results? Coming into the database, only one data value can come from a single file; so how do we populate the other columns of whatever table we copy to?
>
If the file is on the server, you can use pg_read_binary_file() for that purpose.
/Joel
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2021-05-06 16:03:53 | Re: Small issues with CREATE TABLE COMPRESSION |
Previous Message | vignesh C | 2021-05-06 14:53:42 | Re: Printing backtrace of postgres processes |