| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | s-morita(at)beingcorp(dot)co(dot)jp |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7914: pg_dump aborts occasionally |
| Date: | 2013-03-04 20:37:14 |
| Message-ID: | 17113.1362429434@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
s-morita(at)beingcorp(dot)co(dot)jp writes:
> I encountered a strange error during pg_dump as below:
> ----
> pg_dump: Dumping the contents of table "t_file_data" failed: PQgetCopyData()
> failed.
> pg_dump: Error message from server: lost synchronization with server: got
> message type "d", length 21861
Hm. Can you create a reproducible test case for this?
> I think that pqCheckInBufferSpace() should be called only when inBuffer is
> left-justified like this:
> 1432: if (conn->inStart == 0 && pqCheckInBufferSpace(conn->inCursor +
> (size_t) msgLength - 4,
I think changing that code that way would break the considerations
mentioned in pqParseInput3; nor is it clear why this would help, anyway.
It doesn't seem likely that the buffer is so large that it can't be
enlarged by another 20K.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | eshkinkot | 2013-03-04 22:51:46 | BUG #7916: memory leak with array_agg |
| Previous Message | fburgess | 2013-03-04 19:10:14 | Re: Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space. |