| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | vishal_d(at)ureach(dot)com |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dump throws no buffer space available error |
| Date: | 2006-01-19 21:30:11 |
| Message-ID: | 200601192130.k0JLUBg23376@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Vishal Dixit wrote:
> I modified pg_dump.c and aded a sleep of 1000 micro sec in the
> loop for copying data and it fixed the problem. It looks like
> for slower machines when it comes to reading larger tables,
> pg_dump finds no data to read in new lines and assumes EOL while
> there is still data to be dumped, as a result PQendcopy() throws
> error. THROTTLE comments in pg_dump were helpful. Any thoughts.
What operating system is this? It sounds broken.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-19 21:43:03 | Re: Connections not closing |
| Previous Message | Tom Lane | 2006-01-19 21:25:51 | Re: Using rowtype parameter |