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

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Client encoding conversion for binary data (was Re: GUC and postgresql.conf docs)
Date: 2003-05-14 16:27:49
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA4961FAF@m0114.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> We could sidestep that issue if binary I/O for text was in server
> encoding in all cases.

I think that would be reasonable, yes. After all one argument for using
binary mode is speed and efficiency, and not it's editability with
a text editor.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-05-14 16:31:14 Re: passing constant parameters to functional indices
Previous Message Yurgis Baykshtis 2003-05-14 15:59:37 Error building latest contrib/tsearch with 7.3.2