Re: patching the OS of a 9.0.4 db with hot standby

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: Ray Stell <stellr(at)cns(dot)vt(dot)edu>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: patching the OS of a 9.0.4 db with hot standby
Date: 2011-06-01 10:47:51
Message-ID: 4DE618D7.7000102@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Ray Stell wrote:
> I want to do OS patching on prod and hot standby. What is the advised
> procedure for maintenance on the two systems? I would think patching
> the standby should come first in case it blows something up. Oracle has
> a defer switch you can throw on prod to tell it to relax on log shipping
> to the standby. Do we have that here?
>

Your intuition here is reasonable--test on the standby, if things go
wrong consider reversing the patch, with no impact on the master. It's
not covered in the main because that tends not to cross over into OS
management considerations.

The main parameter you could consider tweaking in this case is
wal_keep_segments, which will let you adjust how long the master queues
things for the standby before it gives up. If you really do lose the
standby, you can run out of disk space on the master eventually if you
haven't set this properly.

--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
"PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Glyn Astill 2011-06-01 12:38:22 Reindexing primary keys without locking
Previous Message Greg Smith 2011-06-01 10:23:28 Re: Strange behavior of child table.