Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZSsx0-0003W2-Ta for pgsql-general@arkaria.postgresql.org; Fri, 21 Aug 2015 20:30:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZSswz-0000zQ-Qt for pgsql-general@arkaria.postgresql.org; Fri, 21 Aug 2015 20:30:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZSsum-0006sN-04 for pgsql-general@postgresql.org; Fri, 21 Aug 2015 20:27:52 +0000 Received: from squeakycode.net ([96.126.114.205]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZSsui-0005Y5-G4 for pgsql-general@postgresql.org; Fri, 21 Aug 2015 20:27:51 +0000 Received: from [192.168.10.81] (74-84-91-123.client.mchsi.com [74.84.91.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: andy) by squeakycode.net (Postfix) with ESMTPSA id F29D822989 for ; Fri, 21 Aug 2015 15:27:44 -0500 (CDT) To: pgsql From: Andy Colson Subject: 9.5 beta pg_upgrade documentation Message-ID: <55D789B5.7040308@squeakycode.net> Date: Fri, 21 Aug 2015 15:27:33 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org Hi All. I setup two test VM's with my PG93 database to test upgrading to PG95. I have a primary and standby using wal shipping. The database is about 150Gig, and the two servers (the real servers) are far apart. The vm's are both running on my desktop. I would love to use pg_upgrade on both primary and standby to save from copying 150Gig a very long distance. I'm reading: http://www.postgresql.org/docs/9.5/static/pgupgrade.html At step 9, the first sentence says "If you have ... Log-Shipping ... follow these steps .. before starting any servers". At first I thought a step was missing because it never says to run pg_upgrade on the standby. Then I realized you only run pg_upgrade on the primary then rsync the standby. Would a quick description of the process be helpful? Something like: "If you have Streaming Replication (Section 25.2.5) or Log-Shipping (Section 25.2) standby servers, follow these steps to upgrade them. After you have performed pg_upgrade on the primary don't start it up yet because you can rsync it to the standby for an efficient standby upgrade." I'm confused by step 5 (verify). There are 4 PG instances we're talking about (primary new/old and standby new/old) Which two do I run pg_controldata on? And how does running it "prevent old standby servers from being modified"? And if step 5 requires standby shutdown after the primary, isn't that an important thing to say near the top? Maybe by step 7: Stop both servers. On a side note, I'm confusing myself by the step numbers. There's two step 7's. Can we renumber the step 9 sub steps to be 9.1, 9.2, etc? I think I understand step 9.7, of the four PG instances, "the new master" tells me which to start and stop. Although I'm not sure how long I need to keep it up. Is as fast as I can type enough time? Should I count a few potato's between stop and start? Step 9.8 sounds scary. Can we specifically say that old_pgdata refers to the new pg on the primary and new_pgdata refers to the new pg on the standby? Is that even right? Any chance we could get examples of setting old/new_pgdata? Thanks all on another great release! -Andy -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general