| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GUC and postgresql.conf docs |
| Date: | 2003-05-14 09:09:44 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA4961FAD@m0114.s-mxs.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | greg | 2003-05-14 14:44:04 | Re: fomatting an interval (resend) |
| Previous Message | Sailesh Krishnamurthy | 2003-05-14 07:33:59 | Re: LISTEN/NOTIFY benchmarks? |