"Carrington, Matthew (Produban)" <Matthew.Carrington@xxxxxxxxxxxxxx> writes: > I've tried to explore the issue a bit more using 9.2.1. Here's a trace of the build and dump tests ... As long as you're building your own copy, how about building with --enable-debug and getting a stack trace showing where the error is being thrown? Setting a breakpoint at exit_horribly() ought to do the trick. To be concrete: gdb pg_dump gdb> b exit_horribly gdb> run --port 65432 ... rest of command line for pg_dump ... ... wait for breakpoint to be hit, then ... gdb> bt ... copy and paste the printout here ... gdb> quit regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
