Re: Passing server_encoding to the client is not future-proof

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Passing server_encoding to the client is not future-proof
Date: 2003-08-31 19:09:16
Message-ID: Pine.LNX.4.44.0308312107150.1119-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane writes:

> Peter Eisentraut <peter_e(at)gmx(dot)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(at)gmx(dot)net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2003-08-31 19:09:58 Re: Passing server_encoding to the client is not future-proof
Previous Message Peter Eisentraut 2003-08-31 19:06:17 Re: Passing server_encoding to the client is not future-proof