| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Using pg_upgrade on log-shipping standby servers |
| Date: | 2012-07-10 15:50:18 |
| Message-ID: | 20120710155018.GB31941@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I occasionally get questions about how to run pg_upgrade on log-shipping
standby servers. The attached documentation patch outlines how to do
it.
I don't think we can assume that because pg_upgrade was run on the
master and standby that they are binary identical, can we? Technically
the user file are identical, but the system catalogs and WAL might be
different, hence my suggestion to run rsync before allowing the standby
to rejoin the primary.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| Attachment | Content-Type | Size |
|---|---|---|
| pg_upgrade.diff | text/x-diff | 833 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-07-10 16:00:06 | Re: [PATCH] psql \n shortcut for set search_path = |
| Previous Message | Tom Lane | 2012-07-10 15:49:49 | Re: expression evaluation with expected datatypes |