Re: psql command for bytea output

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(dot)dunstan(at)pgexperts(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql command for bytea output
Date: 2011-10-21 21:35:31
Message-ID: 26058.1319232931@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(dot)dunstan(at)pgexperts(dot)com> writes:
> I also think this is really just a psql issue. Most other clients (e.g.
> a perl DBD::Pg client) will have no trouble handling all this now.

Well, that's debatable, and in any case I think you'd find it will be
easier to push this into COPY than to invent new psql backslash commands
for it.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message nrdb 2011-10-22 00:42:14 database file encryption.
Previous Message Robert Haas 2011-10-21 21:31:41 Re: psql \set vs \copy - bug or expected behaviour?