Received: from maia.hub.org (maia-4.hub.org [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 5EC11632EC0
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue, 11 May 2010 10:16:26 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia,
	port 10024) with ESMTP id 48625-06 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue, 11 May 2010 13:16:19 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from locust.cns.vt.edu (locust.cns.vt.edu [198.82.169.14])
	by mail.postgresql.org (Postfix) with ESMTP id 717DC632DD2
	for <pgsql-admin@postgresql.org>; Tue, 11 May 2010 10:16:19 -0300 (ADT)
Received: by locust.cns.vt.edu (Postfix, from userid 986)
	id 618ED118981; Tue, 11 May 2010 09:16:17 -0400 (EDT)
Date: Tue, 11 May 2010 09:16:17 -0400
From: Ray Stell <stellr@cns.vt.edu>
To: pgsql-admin@postgresql.org
Subject: upgrade proc with pitr standby
Message-ID: <20100511131617.GA17277@cns.vt.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201005/117
X-Sequence-Number: 34590

What are the steps for upgrade of a primary/PITR standby pair to the 
latest 8.3 patchset, 8.3.6-8.3.10?  I don't see this in the docs. 
Should there be something added to 15.4. Upgrading?   

My guess is:
1. turn off the standby config in primary
2. upgrade primary
3. rebuild standby

That way you don't loose the standby if something goes in the toilet.
Is that right?