| From: | Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: psql statements \gstore \gstore_binary (instead COPY RAW) |
| Date: | 2016-12-09 18:48:05 |
| Message-ID: | CACACo5QD3P5rtGD1-f9d1hJEMHujWnXPUQd0iaT_6CSs3c-cpQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Dec 9, 2016 18:40, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> wrote:
Hi
Long time I am pushing a COPY RAW - without success.
Now I propose functionally similar solution - reduced to only to psql
console
Now we have a statement \g for execution query, \gset for exec and store
result in memory and I propose \gstore for storing result in file and
\gstore_binary for storing result in file with binary passing. The query
result should be one row, one column.
Usage:
SELECT image FROM accounts WHERE id = xxx
\gstore_binary ~/image.png
What do you think about this proposal?
I might be missing something, but is it different from:
\t
\a
\o output_filename
SELECT ...
\o
?
--
Alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-12-09 19:02:06 | Re: proposal: psql statements \gstore \gstore_binary (instead COPY RAW) |
| Previous Message | Ian Jackson | 2016-12-09 18:26:31 | [OSSTEST PATCH 1/1] PostgreSQL db: Retry transactions on constraint failures |