From: | Steve Krall <swalker(at)iglou(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump on older version of postgres eating huge |
Date: | 2004-03-19 15:51:14 |
Message-ID: | Pine.LNX.4.58.0403191029520.27168@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I've done this with the debug level all the way up...
You can get the file here( 20 megs uncompressed, 130K compressed ):
http://www.papajohns.com/postgres/postgres.log.bz2
While this dump was running, top reported that pg_dump was taking up
around 500-550megs. Then the machine stopped responding.
If you need anything else, just ask.
Steve
On Thu, 18 Mar 2004, Tom Lane wrote:
> Steve Krall <swalker(at)iglou(dot)com> writes:
> > When doing a pg_dump databasename > file.dmp pg_dump eats up all the
> > memory, and is eventually killed because it takes
> > up a huge amount of memory. The dump file is always 0 bytes. It works
> > perfectly fine on our other server.
>
> > When we run pg_dump in verbose mode, it is trying to get the trigger
> > information.
>
> Can you run it with query logging turned on, so we can see what query(s)
> it's issuing while it eats RAM?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2004-03-19 16:08:09 | Re: unsigned types, binary op. and cast pb |
Previous Message | Richard Huxton | 2004-03-19 15:49:27 | Re: transactions in plpgsql |