Re: Client encoding conversion for binary data (was Re: GUC and postgresql.conf docs)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hannu Krosing <hannu(at)tm(dot)ee>
Cc: Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Client encoding conversion for binary data (was Re: GUC and postgresql.conf docs)
Date: 2003-05-15 12:54:51
Message-ID: 7687.1053003291@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hannu Krosing <hannu(at)tm(dot)ee> writes:
> I have not been closely following the discussion about FE/BE protocol
> changes, but the way converting binary seems dangerous - if you insert a
> .gif file into bytea column using decode(encodedgiffile,'base64'), but
> would like to get it out in binary for performance reasons, it is not
> good if it gets run through conversion routines.

bytea does not get converted in any case. The issue here is what to do
about text datatypes.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Cédric Coulon 2003-05-15 13:46:18 predict conflict
Previous Message Christopher Kings-Lynne 2003-05-15 08:20:08 Re: Client encoding conversion for binary data (was Re: