pg_dump core dumping

Hi All,

 Got a weird issue that I'm running into when attempting to dump a
database under PostgreSQL 7.2.4. The OS is FreeBSD 4.8, with ~100 GBytes
RAID and 4 Gig's of RAM. The pg_dump  command is:

pg_dump -U pgsql -S pgsql -D -F p -f test.sql test

 When I try to dump the database, she appears to follow through fine,
and top show's that she get's up to about 512 MBytes of RAM in use then
core dumps. the output file (test.sql) is never even written to, however
the ~512 MByte core file is left behind (obviously :>). One thing that
has be curious, is why the system is even loading up that much RAM, as
the database itself is only ~46 MBytes:

test# du -skc 16717879
46300   16717879
46300   total

 The system has loaded of free disk space , and the user (root) has
permissions to write to the folder I'm dumping the file to. Here is a
back trace of the core file, as this is my first report to the bugs
list, let me know if there is anything else I can send that might help.

(gdb) bt
#0  0x280880ac in getRowDescriptions (conn=0x8068200) at fe-exec.c:1027
#1  0x28087eaa in parseInput (conn=0x8068200) at fe-exec.c:919
#2  0x28088525 in PQgetResult (conn=0x8068200) at fe-exec.c:1249
#3  0x280886b9 in PQexec (conn=0x8068200, query=0x8076600 "SELECT adsrc
from pg_attrdef where adrelid = '16721225'::oid and adnum = 8 ") at
fe-exec.c:1362
#4  0x804ee92 in getTableAttrs ()
#5  0x80530fa in dumpSchema ()
#6  0x804af64 in main ()
#7  0x8049b4a in _start (arguments=0x7fbffc90
"/vm/.t/usr/ports/local/postgresql-7.2.4/src/bin/pg_dump/pg_dump") at
/usr/src/lib/csu/i386-elf/crt1.c:119

--
Chris Bowlby <excalibur@hub.org>
Hub.Org Networking Services