From: | "Marc Watson" <mark(dot)watson(at)jurisconcept(dot)ca> |
---|---|
To: | "Craig Ringer" <ringerc(at)ringerc(dot)id(dot)au>, <mmoncure(at)gmail(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: 32-bit libpq with 64-bit server |
Date: | 2012-06-21 11:37:57 |
Message-ID: | 3AEA66C4C2E030449E8020F9E42E558553437E@sbs2k3.JurisConcept.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----Message d'origine-----
De : Merlin Moncure [mailto:mmoncure(at)gmail(dot)com]
Envoyé : June-20-12 11:36 AM
It should pretty much work. The main thing to watch out for is that very large results sets will hit the upper limit on memory allocations.
merlin
De : Craig Ringer [mailto:ringerc(at)ringerc(dot)id(dot)au]
Envoyé : June-20-12 10:47 PM
On 06/20/2012 11:07 PM, Marc Watson wrote:
Hello all,
On Windows, I have a 32-bit client application that uses the 32-bit libpq.dll. In testing the client application with a Postgres 9.2 64-bit server I've noticed no problems, and was wondering if anyone knows of any caveats in this - AFAICS the tcp communication is between the 32-bit libpq and the 64-bit backend is compatible.
Unless you go to considerable efforts to ensure otherwise, the protocol is text-based and isn't affected by endianness or word size. I'm not sure about the binary protocol, but it's rarely used.
--
Craig Ringer
Thanks Craig and Merlin. I'll continue with my testing of 9.2-64 bit.
Mark Watson
From | Date | Subject | |
---|---|---|---|
Next Message | Dickson S. Guedes | 2012-06-21 11:40:11 | Re: Output of query_to_xml |
Previous Message | Evan Martin | 2012-06-21 10:03:19 | Re: Please make it easy to drop a database that is in use |