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 <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] > ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
