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