From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Shachar Shemesh <shachar(at)shemesh(dot)biz> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Julian Heeb <heebj2000(at)yahoo(dot)de>, oledb-devel(at)pgfoundry(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: [Oledb-dev] double precision error with pg linux server, but not with windows pg server |
Date: | 2007-05-19 21:36:07 |
Message-ID: | 464F6DC7.4040904@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Shachar Shemesh wrote:
>> Perhaps OLE is trying to use binary instead of text transmission of
>> data?
>>
> Of course it does. That's what the OLE DB specs say. Said so in my
> original email.
>
Why the heck do the OLE DB specs care about the internals of the
client-server prototocol? It is documented fairly clearly that text is
the only portable way to transfer data.
Perhaps we need to expand this sentence in the docs: "Keep in mind that
binary representations for complex data types may change across server
versions;"
The COPY docs are probably more correct: "The BINARY key word causes all
data to be stored/read as binary format rather than as text. It is
somewhat faster than the normal text mode, but a binary-format file is
less portable across machine architectures and PostgreSQL versions."
I do recall someone telling me that text mode transfer could actually be
faster than binary, somewhat to their (and my) surprise.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-05-19 21:44:22 | Re: Re: [Oledb-dev] double precision error with pg linux server, but not with windows pg server |
Previous Message | Tom Lane | 2007-05-19 21:22:18 | Re: Re: [Oledb-dev] double precision error with pg linux server, but not with windows pg server |