Re: [HACKERS] proposal: psql statements \gstore \gstore_binary (instead COPY RAW) - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] proposal: psql statements \gstore \gstore_binary (instead COPY RAW)
Date
Msg-id CAFj8pRBchJEaTKMGvko5FqCUr9BhDPdBcsBF0GRyRZUBQxwx-Q@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] proposal: psql statements \gstore \gstore_binary (instead COPY RAW)  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers


2016-12-11 18:23 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com>:
Hi

2016-12-09 18:39 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com>:
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?

here is a poc patch

Regards

Pavel

Usage:

postgres=# set client_encoding to 'latin2';
SET
Time: 1,561 ms
postgres=# select a from foo
postgres-# \gbstore ~/doc.xml
Time: 1,749 ms

content of doc.xml
<?xml version="1.0" encoding="LATIN2"?><a>příliš žluťoučký kůň se napil žluté vody</a>


second update - + doc

the export import regress tests are little bit heavy - I'll write it for loading content file together.

Regards

Pavel
 

Regards

Pavel


Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] pgcrypto compilation error due to stack-allocated EVP_CIPHER_CTX
Next
From: Heikki Linnakangas
Date:
Subject: Re: [HACKERS] Broken SSL tests in master