Re: [HACKERS] export import bytea from psql
От | Daniel Verite |
---|---|
Тема | Re: [HACKERS] export import bytea from psql |
Дата | |
Msg-id | 210f4991-b263-461c-8124-ff509427d73a@manitou-mail.org обсуждение исходный текст |
Ответ на | Re: [HACKERS] export import bytea from psql (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: [HACKERS] export import bytea from psql
|
Список | pgsql-hackers |
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. Best regards, -- Daniel Vérité PostgreSQL-powered mailer: http://www.manitou-mail.org Twitter: @DanielVerite
В списке pgsql-hackers по дате отправления: