Re: Re: new set of psql patches for loading (saving) data from (to) text, binary files

From: Andres Freund <andres(at)anarazel(dot)de>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Jason O'Donnell <odonnelljp01(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: new set of psql patches for loading (saving) data from (to) text, binary files
Date: 2017-04-05 23:01:31
Message-ID: 20170405230131.7hrtqdwpcvsgi3aa@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2017-03-18 17:51:48 +0100, Pavel Stehule wrote:
> What is done:
>
> create table foo foo(a bytea);
>
> -- import
> insert into foo values($1)
> \gloadfrom ~/xxx.jpg bytea
>
> -- export
> \pset format binary
> select a from foo
> \g ~/xxx2.jpg
>
> tested on import 55MB binary file
>
> Comments, notes?
>
> Available import formats are limited to text, bytea, xml - these formats
> are safe for receiving data via recv function.

I don't think we have design agreement on this at this point. Given the
upcoming code freeze, I think we'll have to hash this out during the
next development cycle. Any counterarguments?

- Andres

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-04-05 23:04:49 Re: scram and \password
Previous Message Pierre Ducroquet 2017-04-05 22:59:49 Bug with pg_basebackup and 'shared' tablespace