Re: GUC and postgresql.conf docs - Mailing list pgsql-hackers

From Zeugswetter Andreas SB SD
Subject Re: GUC and postgresql.conf docs
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA4961FAD@m0114.s-mxs.net
Whole thread Raw
In response to GUC and postgresql.conf docs  (Josh Berkus <josh@agliodbs.com>)
Responses Client encoding conversion for binary data (was Re: GUC and postgresql.conf docs)
List pgsql-hackers
> Binary-encoded numeric values don't go through
> encoding conversion.  Text strings currently do.  The only place where I
> had any difficulty deciding what a particular datatype should do is with
> the 1-byte "char" type, which has a foot in both camps.  I decided to
> treat it as an unconverted single byte (but am willing to listen to
> argument if anyone thinks differently).

One concern I would have is how to get at the raw unconverted text data
without changing the client encoding. I do not really see an advantage in
providing the same thing for text and binary format if it is now
a per column thing. I would do text unconverted if binary format is selected
for that column.

Did COPY BINARY convert text ?

Andreas


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Text format protocol representation
Next
From: Bruce Badger
Date:
Subject: Re: Text format protocol representation