| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tomas Berndtsson <tomas(at)nocrew(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: big text field -> message type 0x44 |
| Date: | 2002-12-04 21:17:18 |
| Message-ID: | 18432.1039036638@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tomas Berndtsson <tomas(at)nocrew(dot)org> writes:
> However, after some semi-random looking through the source code of
> libpq, I tried to change a value, namely here:
> fe-misc.c row 510 in pqReadData():
> if (conn->inEnd > 32768 &&
> (conn->inBufSize - conn->inEnd) >= 8192)
> I changed the 32768 value to 131072, and sure enough, my application
> was able to get larger fields without any errors.
That's really interesting. I cannot see anything unsafe about that
retry loop --- could you instrument it some more to determine exactly
what happens after we go back to try to read more?
Also, are you using SSL by any chance? Perhaps the problem is that
the SSL library doesn't react the same as a bare recv() call?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Patrick Welche | 2002-12-04 21:33:17 | 24:00:00 ? |
| Previous Message | Tom Lane | 2002-12-04 20:58:24 | Re: postgres core FALSE ALARM |