Thread: statically linked pg_dump
ISTR this question coming up before, but I couldn't find an answer. Is there a reason we don't build versions of pg_dump and pg_dumpall that are statically linked against libpq so they can be run uninstalled as part of a migration process? I should have thought that this would be extremely easy - just a few Makefile changes. Then the recommended procedure could go 1. build. 2 dump using static pg_dump/pg_dumpall. 3 stop old server. 4 move old installation aside. 5. install new build. 6 initdb. 7 restore. cheers andrew
> ISTR this question coming up before, but I couldn't find an answer. Is > there a reason we don't build versions of pg_dump and pg_dumpall that > are statically linked against libpq so they can be run uninstalled as > part of a migration process? I should have thought that this would be > extremely easy - just a few Makefile changes. Then the recommended > procedure could go 1. build. 2 dump using static pg_dump/pg_dumpall. 3 > stop old server. 4 move old installation aside. 5. install new build. 6 > initdb. 7 restore. +1 Just add -static to the CFLAGS in src/bin/pg_dump/Makefile IIRC. I do this all the time :) Chris