Re: Passing server_encoding to the client is not future-proof - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Passing server_encoding to the client is not future-proof
Date
Msg-id Pine.LNX.4.44.0308312107150.1119-100000@peter.localdomain
Whole thread Raw
In response to Re: Passing server_encoding to the client is not future-proof  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane writes:

> Peter Eisentraut <peter_e@gmx.net> writes:
> > Tom Lane writes:
> >> One of the reasons for not doing conversion in binary mode is to have an
> >> escape hatch for unconvertible characters, eg for dump purposes.
>
> > That functionality is already provided by setting the client encoding to
> > SQL_ASCII.
>
> Hm.  Okay, so are you arguing that we should not remove encoding
> conversion from the binary-transmission case?

I think a binary mode for text is pretty useless, at least compared to
binary modes for numbers and other data types, where they are clearly
useful.  Therefore, we should keep the binary mode the same as the normal
mode and just label it "binary".  (I assume it's not practical to not have
a binary mode for particular data types.)

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Passing server_encoding to the client is not future-proof
Next
From: Peter Eisentraut
Date:
Subject: Re: Passing server_encoding to the client is not future-proof