| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: statically linked pg_dump |
| Date: | 2005-08-22 01:54:18 |
| Message-ID: | 4309304A.8070007@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-08-22 01:56:56 | New web page for release status |
| Previous Message | Tom Lane | 2005-08-22 01:50:10 | Re: Pre-allocated free space for row updating (like PCTFREE) |