Vishal Dixit <[EMAIL PROTECTED]> writes:
> 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
This is Windows 2000 Server, 2.00GHz Pentium.
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
---(end of broadcast)---
TIP 3: Have you checked our extensi
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
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 PQe
"Vishal Dixit" <[EMAIL PROTECTED]> wrote
>
> We are running postgres version 8.0 on windows server 2003. On
> doing a pg_dump of a large database the following error occurs:
>
> pg_dump: could not receive data from server: No buffer space
> available
>
> There is one table in the database containi
