Re: [HACKERS] export import bytea from psql - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] export import bytea from psql
Date
Msg-id CAFj8pRB4P=6Kv4owZi7K1iHUOtnKUnRpZshTL+4JVFx_52UccA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] export import bytea from psql  ("Daniel Verite" <daniel@manitou-mail.org>)
List pgsql-hackers


2017-05-11 17:16 GMT+02:00 Daniel Verite <daniel@manitou-mail.org>:
        Pavel Stehule wrote:

> It is similar to my first or second proposal - rejected by Tom :(

Doesn't it differ? ISTM that in the patches/discussion related to:
https://commitfest.postgresql.org/11/787/
it was proposed to change \set in one way or another,
and also in the point #1 of this present thread:

> > 1. using psql variables - we just need to write commands \setfrom
> > \setfrombf - this should be very simple implementation. The value can be
> > used more times. On second hand - the loaded variable can hold lot of
> > memory (and it can be invisible for user).


My comment is: let's not change \set or even create a variant
of it just for importing verbatim file contents, in text or binary,
because interpolating psql variables differently in the query itself
is all we need.

There was 100% agreement on format and then discussion finished without any result.

Regards

Pavel
 


Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] eval_const_expresisions and ScalarArrayOpExpr
Next
From: Simon Riggs
Date:
Subject: Re: [HACKERS] Safer and faster get_attstatsslot()