On Sat, Sep 14, 2013 at 6:40 PM, Robert Nix <rob...@urban4m.com> wrote:
> Running a pg_upgrade task is causing Segmentation fault: > > command: "/usr/lib/postgresql/9.3/bin/pg_dump" --host > "/var/lib/postgresql" --port 50432 --username "postgres" --schema-only > --quote-all-identifiers --binary-upgrade --format=custom > --file="pg_upgrade_dump_6064585.custom" "u" >> > "pg_upgrade_dump_6064585.log" 2>&1 > pg_dump: row number 0 is out of range 0..-1 > Segmentation fault (core dumped) > ... > > Any tips on how to diagnose and/or what might be the problem? > What happens if you manually run the pg_dump command quoted above against a running 9.1 server, outside of the context of pg_upgrade? (Your port will be probably be different from 50432) If that still crashes, What if you drop the --binary-upgrade option? The --format=custom option? > > gdb doesn't seem helpful: > > $ gdb /usr/lib/postgresql/9.3/bin/pg_dump core > GNU gdb (GDB) 7.5-ubuntu > Reading symbols from /usr/lib/postgresql/9.3/bin/pg_dump...(no debugging > symbols found)...done. > You need to install the debugging symbols, which I have no experience doing under Ubuntu, but it should be easy to find instructions for. Or you could compile pg_dump from source, after configuring with --enable-debug. Cheers, Jeff
