Re: Large queries - again...

From: "Steve Howe" <howe(at)carcass(dot)dhs(dot)org>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Large queries - again...
Date: 2001-07-20 21:46:26
Message-ID: 008e01c11165$6d4a27b0$7e31b0c8@angla
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Steve Howe" <howe(at)carcass(dot)dhs(dot)org>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Sent: Friday, July 20, 2001 5:17 PM
Subject: Re: [HACKERS] Large queries - again...

> "Steve Howe" <howe(at)carcass(dot)dhs(dot)org> writes:
> > It returns "Error: pqReadData() -- read() failed: errno=0 No
error
> > " as expected when a nil pointer is returned.
>
> "As expected"? That's not what I'd expect, especially not for a
> behavior that's dependent on the size of an *outgoing* message.
It is expected, because it's the default message when a PQexec() query
returns NULL: pqReadData() will return nothing yet no error is signed.
Of course, the "really expected" would be a sucessfull exec :-)

> (Thinks for awhile...) You're not using PQsetnonblocking() are you,
> by any chance?
No, I'm not. Asynchronous libpq connections on Windows are still not
realiable (althought I read someone submitted a patch recently), so I'm
keeping synchronous queries for a while. I'm not also using any non-standard
functions; just plain PQconnectdb() and PQexec()...

Best Regards,
Steve

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 2001-07-20 22:16:58 Re: RPM source files should be in CVS (was Re: [GENERAL] psql -l)
Previous Message Tom Lane 2001-07-20 21:14:44 Re: RPM source files should be in CVS (was Re: psql -l)