Re: Client encoding conversion for binary data (was Re: GUC and postgresql.conf docs) - Mailing list pgsql-hackers

From Zeugswetter Andreas SB SD
Subject Re: Client encoding conversion for binary data (was Re: GUC and postgresql.conf docs)
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA4961FAF@m0114.s-mxs.net
Whole thread Raw
In response to Client encoding conversion for binary data (was Re: GUC and postgresql.conf docs)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Client encoding conversion for binary data (was Re: GUC and postgresql.conf docs)
List 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


pgsql-hackers by date:

Previous
From: "Yurgis Baykshtis"
Date:
Subject: Error building latest contrib/tsearch with 7.3.2
Next
From: Tom Lane
Date:
Subject: Re: passing constant parameters to functional indices