From: | Kelly Burkhart <kelly(dot)burkhart(at)gmail(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Binary params in libpq |
Date: | 2011-03-01 14:19:45 |
Message-ID: | AANLkTin4jDSVmMfczkQwiXNQq19k2Jd3zhZ25e6Y8bRD@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Feb 28, 2011 at 8:42 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Sun, Feb 27, 2011 at 7:39 PM, Craig Ringer
>> AFAIK, the `timestamp' type moved from a floating-point to an integer
>> representation internally, which would've affected the binary protocol
>> representation. That was even a compile-time config option, so it could be
>> different between two different Pg installs with the same version.
>
> Actually, this has always been a compile time option on the server as
> far as i remember and there is protocol support for it -- libpq tells
> you how it has been set...you've always had to deal with this
I don't see any libpq calls that can, at run-time, tell you things
like what format the timestamp is and what endian-ness the server is.
Is there something I'm missing? The only thing I could figure out is
to do something like 'select 123::int4' or select a known date and
determine the nature of the server from what you get back.
-K
From | Date | Subject | |
---|---|---|---|
Next Message | Alan Acosta | 2011-03-01 14:23:49 | Re: Lock ACCESS EXCLUSIVE and Select question ! |
Previous Message | Ray Stell | 2011-03-01 13:09:43 | Re: Postgresql not start during Startup |