Re: pg_dump - lost synchronization with server: got message type "d", length 6036499

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Klint Gore <kgore4(at)une(dot)edu(dot)au>
Cc: pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_dump - lost synchronization with server: got message type "d", length 6036499
Date: 2008-07-03 01:02:26
Message-ID: 19488.1215046946@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Klint Gore <kgore4(at)une(dot)edu(dot)au> writes:
> Tom Lane wrote:
>> Maybe it's
>> dying here after having leaked a lot of memory for some other reason
>> --- try watching the pg_dump process size while it runs.

> Peak memory usage was about 540m which brought the total usage for the
> machine to about half the physical memory allocated (3g total).

Well, that might well explain the failure. pg_dump does suck a lot of
schema information into memory at startup, but 540m seems excessive.
Maybe you've found a memory leak in pg_dump (it wouldn't be the first
one). Does this database have a particularly large number of objects?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Matt Magoffin 2008-07-03 01:19:27 Re: Memory use in 8.3 plpgsql with heavy use of xpath()
Previous Message Klint Gore 2008-07-03 00:49:10 Re: pg_dump - lost synchronization with server: got message type "d", length 6036499