Re: proposal: psql statements \gstore \gstore_binary (instead COPY RAW)

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: psql statements \gstore \gstore_binary (instead COPY RAW)
Date: 2016-12-09 19:02:06
Message-ID: CAFj8pRCMzXkgcMW+qTdZWabZ32XgFoKOTAKULvkO98qO_VnwQA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2016-12-09 19:48 GMT+01:00 Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>:

> 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
>
> ?
>
>
The \gstore is same like these commands - but it is user friendly - one
liner statement.

For \gstore_binary there is not any workaround

Pavel

> --
> Alex
>
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2016-12-09 20:33:25 Re: new table partitioning breaks \d table to older versions
Previous Message Oleksandr Shulgin 2016-12-09 18:48:05 Re: proposal: psql statements \gstore \gstore_binary (instead COPY RAW)