]>; <[EMAIL PROTECTED]>
Sent: Sunday, July 29, 2001 8:57 PM
Subject: Re: [HACKERS] LIBPQ on Windows and large Queries
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> > Well haven't this problem solved already ?
>
> I'm not sure. Steve, have you tried curr
Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> Well haven't this problem solved already ?
I'm not sure. Steve, have you tried current sources?
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe comman
Tom Lane wrote:
>
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> > Yes it's real.
> > Error handling seems the cause.
>
> Hmm, are you working with CVS tip or 7.1.* sources? I'm wondering
> how this interacts with the recent patch to #define errno as
> WSAGetLastError() on WIN32...
>
Oops sorry
Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> Yes it's real.
> Error handling seems the cause.
Hmm, are you working with CVS tip or 7.1.* sources? I'm wondering
how this interacts with the recent patch to #define errno as
WSAGetLastError() on WIN32...
regards, tom lane
--
Tom Lane wrote:
>
> "Steve Howe" <[EMAIL PROTECTED]> writes:
> > Is anybody trying to solve the 8191 bytes query limit from libpq
> > windows port ???
>
> FWIW, if the problem is real (which I still misdoubt),
Yes it's real.
Error handling seems the cause. When "Error: pqReadData() --
r
At 01:36 27.07.2001 -0400, you wrote:
>"Steve Howe" <[EMAIL PROTECTED]> writes:
> > Is anybody trying to solve the 8191 bytes query limit from libpq
> > windows port ???
>
>I think it's *your* responsibility, at least to identify what's going
>on. This is an open source project, and that
"Steve Howe" <[EMAIL PROTECTED]> writes:
> Is anybody trying to solve the 8191 bytes query limit from libpq
> windows port ???
I think it's *your* responsibility, at least to identify what's going
on. This is an open source project, and that means you can and should
fix problems that aff
I'm surprised you are even able to run postgres in windows. I
didn't even know postgres supported windows. Could you kindly point me to
instructions on how to run it and build the postgres souce on windows? If
nobody will try to fix it, then maybe we should just try it ourseleves and
po
