Thread: Fw: SQL Error: pqReadData() -- read() failed: errno=0 No error

Fw: SQL Error: pqReadData() -- read() failed: errno=0 No error

From
"Derrick Betts"
Date:
I am a Postgres novice.  I have not done anything in the way of configuring
the DB differently from what the defaults are.

Here is my problem...
     I am sending the source text from web pages to the DB (7.3.2) through a
dataset in Delphi.  The field in the DB table is of the type "text", and the
fieldtype in Delphi shows ftMemo (a Blob type).  When I "ApplyUpdates" from
my application I get the "SQL Error: pqReadData() --  read() failed: errno=0
No error"  message.

Now, this is only happening when the length of the text that I am
attempting
to update to the DB is large.  On smaller text string sizes (ie. simple Web
Pages), I get no error and everything posts fine.

Is there some sort of setting that needs to be set for large "text" strings
on the DB, or is it likely to be an issue with the dataset - ApplyUpdates
procedure inside Delphi?

Is there a way to increase the buffer for incoming  requests?  Will this
help?


Thanks,
Derrick


Re: Fw: SQL Error: pqReadData() -- read() failed: errno=0 No error

From
Tom Lane
Date:
"Derrick Betts" <Derrick@grifflink.com> writes:
>      I am sending the source text from web pages to the DB (7.3.2) through a
> dataset in Delphi.  The field in the DB table is of the type "text", and the
> fieldtype in Delphi shows ftMemo (a Blob type).  When I "ApplyUpdates" from
> my application I get the "SQL Error: pqReadData() --  read() failed: errno=0
> No error"  message.

> Now, this is only happening when the length of the text that I am
> attempting
> to update to the DB is large.

Are you using an SSL-encrypted connection?  Some versions of libpq could
create this failure with SSL.  Unfortunately, the first version that
really works *reliably* with SSL is not yet released :-( ... 7.3.2
through 7.3.4 misbehave even worse than the 7.3 or 7.3.1 libpq you
appear to be using.  I believe that the problems are finally fixed as of
CVS tip, but I do not know when or whether there will be a 7.3.5.
Instead of waiting, your best bet might be to pull the tip of the
REL7_3_STABLE branch from our CVS server (see
http://developer.postgresql.org/docs/postgres/cvs.html) and build libpq
from it.

Or, don't use SSL ...

            regards, tom lane

Re: Fw: SQL Error: pqReadData() -- read() failed: errno=0 No error

From
"Derrick Betts"
Date:
Thank you very much for your input.  I will look over the options you have
suggested. :)

Derrick

----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Derrick Betts" <Derrick@grifflink.com>
Cc: <pgsql-novice@postgresql.org>
Sent: Monday, September 08, 2003 9:59 AM
Subject: Re: [NOVICE] Fw: SQL Error: pqReadData() -- read() failed: errno=0
No error


> "Derrick Betts" <Derrick@grifflink.com> writes:
> >      I am sending the source text from web pages to the DB (7.3.2)
through a
> > dataset in Delphi.  The field in the DB table is of the type "text", and
the
> > fieldtype in Delphi shows ftMemo (a Blob type).  When I "ApplyUpdates"
from
> > my application I get the "SQL Error: pqReadData() --  read() failed:
errno=0
> > No error"  message.
>
> > Now, this is only happening when the length of the text that I am
> > attempting
> > to update to the DB is large.
>
> Are you using an SSL-encrypted connection?  Some versions of libpq could
> create this failure with SSL.  Unfortunately, the first version that
> really works *reliably* with SSL is not yet released :-( ... 7.3.2
> through 7.3.4 misbehave even worse than the 7.3 or 7.3.1 libpq you
> appear to be using.  I believe that the problems are finally fixed as of
> CVS tip, but I do not know when or whether there will be a 7.3.5.
> Instead of waiting, your best bet might be to pull the tip of the
> REL7_3_STABLE branch from our CVS server (see
> http://developer.postgresql.org/docs/postgres/cvs.html) and build libpq
> from it.
>
> Or, don't use SSL ...
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
>