pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
upgrade proc with pitr standby
5+ messages / 3 participants
[nested] [flat]

* upgrade proc with pitr standby
@ 2010-05-11 13:16 Ray Stell <stellr@cns.vt.edu>
  2010-05-11 13:29 ` Re: upgrade proc with pitr standby Devrim GÜNDÜZ <devrim@gunduz.org>
  0 siblings, 1 reply; 5+ messages in thread

From: Ray Stell @ 2010-05-11 13:16 UTC (permalink / raw)
  To: pgsql-admin

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?



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: upgrade proc with pitr standby
  2010-05-11 13:16 upgrade proc with pitr standby Ray Stell <stellr@cns.vt.edu>
@ 2010-05-11 13:29 ` Devrim GÜNDÜZ <devrim@gunduz.org>
  2010-05-13 14:25   ` Re: upgrade proc with pitr standby Ray Stell <stellr@cns.vt.edu>
  0 siblings, 1 reply; 5+ messages in thread

From: Devrim GÜNDÜZ @ 2010-05-11 13:29 UTC (permalink / raw)
  To: Ray Stell <stellr@cns.vt.edu>; +Cc: pgsql-admin

On Tue, 2010-05-11 at 09:16 -0400, Ray Stell wrote:
> 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 

You need to upgrade standby first, restart it. Then, upgrade master and
restart it. No need to turn off standby config.

Regards,
-- 
Devrim GÜNDÜZ
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
PostgreSQL RPM Repository: http://yum.pgrpms.org
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org  Twitter: http://twitter.com/devrimgunduz

Attachments:

  signature.asc (application/pgp-signature, 197B) download

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: upgrade proc with pitr standby
  2010-05-11 13:16 upgrade proc with pitr standby Ray Stell <stellr@cns.vt.edu>
  2010-05-11 13:29 ` Re: upgrade proc with pitr standby Devrim GÜNDÜZ <devrim@gunduz.org>
@ 2010-05-13 14:25   ` Ray Stell <stellr@cns.vt.edu>
  2010-05-13 14:31     ` Re: upgrade proc with pitr standby Kevin Grittner <Kevin.Grittner@wicourts.gov>
  0 siblings, 1 reply; 5+ messages in thread

From: Ray Stell @ 2010-05-13 14:25 UTC (permalink / raw)
  To: Devrim G?ND?Z <devrim@gunduz.org>; +Cc: pgsql-admin

On Tue, May 11, 2010 at 04:29:18PM +0300, Devrim G?ND?Z wrote:
> On Tue, 2010-05-11 at 09:16 -0400, Ray Stell wrote:
> > 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 
> 
> You need to upgrade standby first, restart it. Then, upgrade master and
> restart it. No need to turn off standby config.

do you know why might be going south?

the standby is applying WAL:
----------------------------
,30357,,2010-05-12 17:04:33.927 EDT,4beb17d2.7695,5,2010-05-12 17:04:18 EDT,0, LOG:  automatic recovery in progress
,30357,,2010-05-12 17:04:34.534 EDT,4beb17d2.7695,6,2010-05-12 17:04:18 EDT,0, LOG:  redo starts at 0/567D982C
,30357,,2010-05-12 17:04:34.630 EDT,4beb17d2.7695,7,2010-05-12 17:04:18 EDT,0, LOG:  restored log file "000000020000000000000057" from archive
,30357,,2010-05-12 17:04:35.315 EDT,4beb17d2.7695,8,2010-05-12 17:04:18 EDT,0, LOG:  restored log file "000000020000000000000058" from archive
...

,30357,,2010-05-12 17:05:21.555 EDT,4beb17d2.7695,23,2010-05-12 17:04:18 EDT,0, LOG:  restored log file "000000020000000000000067" from archive
,30357,,2010-05-12 17:05:22.408 EDT,4beb17d2.7695,24,2010-05-12 17:04:18 EDT,0, LOG:  restored log file "000000020000000000000068" from archive


shutdown standby:
-----------------
,30355,,2010-05-13 08:59:49.547 EDT,4beb17d2.7693,1,2010-05-12 17:04:18 EDT,0, LOG:  received fast shutdown request
,30357,,2010-05-13 08:59:49.547 EDT,4beb17d2.7695,25,2010-05-12 17:04:18 EDT,0, FATAL:  could not restore file "000000020000000000000069" from archive: return code 15
,30355,,2010-05-13 08:59:49.551 EDT,4beb17d2.7693,2,2010-05-12 17:04:18 EDT,0, LOG:  startup process (PID 30357) exited with exit code 1
,30355,,2010-05-13 08:59:49.551 EDT,4beb17d2.7693,3,2010-05-12 17:04:18 EDT,0, LOG:  aborting startup due to startup process failure


flip to 8.3.10 and restart standby:
-----------------------------------
,3440,,2010-05-13 09:06:35.720 EDT,4bebf95b.d70,1,2010-05-13 09:06:35 EDT,0, LOG:  database system was interrupted while in recovery at log time 2010-05-12 17:01:05 EDT
,3440,,2010-05-13 09:06:35.720 EDT,4bebf95b.d70,2,2010-05-13 09:06:35 EDT,0, HINT:  If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
,3440,,2010-05-13 09:06:35.720 EDT,4bebf95b.d70,3,2010-05-13 09:06:35 EDT,0, LOG:  starting archive recovery
,3440,,2010-05-13 09:06:35.732 EDT,4bebf95b.d70,4,2010-05-13 09:06:35 EDT,0, LOG:  restore_command = '/usr/local/pgsql/bin/pg_standby  /data/pgsql/wals/alerts_oamp %f %p %r'
sh: /usr/local/pgsql/bin/pg_standby: No such file or directory
,3440,,2010-05-13 09:06:35.734 EDT,4bebf95b.d70,5,2010-05-13 09:06:35 EDT,0, FATAL:  could not restore file "00000002.history" from archive: return code 32512
,3438,,2010-05-13 09:06:35.735 EDT,4bebf95b.d6e,1,2010-05-13 09:06:35 EDT,0, LOG:  startup process (PID 3440) exited with exit code 1
,3438,,2010-05-13 09:06:35.735 EDT,4bebf95b.d6e,2,2010-05-13 09:06:35 EDT,0, LOG:  aborting startup due to startup process failure



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: upgrade proc with pitr standby
  2010-05-11 13:16 upgrade proc with pitr standby Ray Stell <stellr@cns.vt.edu>
  2010-05-11 13:29 ` Re: upgrade proc with pitr standby Devrim GÜNDÜZ <devrim@gunduz.org>
  2010-05-13 14:25   ` Re: upgrade proc with pitr standby Ray Stell <stellr@cns.vt.edu>
@ 2010-05-13 14:31     ` Kevin Grittner <Kevin.Grittner@wicourts.gov>
  2010-05-13 16:04       ` Re: upgrade proc with pitr standby Ray Stell <stellr@cns.vt.edu>
  0 siblings, 1 reply; 5+ messages in thread

From: Kevin Grittner @ 2010-05-13 14:31 UTC (permalink / raw)
  To: Ray Stell <stellr@cns.vt.edu>; Devrim G?ND?Z <devrim@gunduz.org>; +Cc: pgsql-admin

Ray Stell <stellr@cns.vt.edu> wrote:
> ,3440,,2010-05-13 09:06:35.734 EDT,4bebf95b.d70,5,2010-05-13
> 09:06:35 EDT,0,FATAL:  could not restore file "00000002.history"
> from archive: return code 32512
 
Return code 32512?  I think you'd be OK if your recovery script
returned 1 when it didn't find this file.
 
-Kevin



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: upgrade proc with pitr standby
  2010-05-11 13:16 upgrade proc with pitr standby Ray Stell <stellr@cns.vt.edu>
  2010-05-11 13:29 ` Re: upgrade proc with pitr standby Devrim GÜNDÜZ <devrim@gunduz.org>
  2010-05-13 14:25   ` Re: upgrade proc with pitr standby Ray Stell <stellr@cns.vt.edu>
  2010-05-13 14:31     ` Re: upgrade proc with pitr standby Kevin Grittner <Kevin.Grittner@wicourts.gov>
@ 2010-05-13 16:04       ` Ray Stell <stellr@cns.vt.edu>
  0 siblings, 0 replies; 5+ messages in thread

From: Ray Stell @ 2010-05-13 16:04 UTC (permalink / raw)
  To: Kevin Grittner <Kevin.Grittner@wicourts.gov>; +Cc: Devrim G?ND?Z <devrim@gunduz.org>; pgsql-admin

On Thu, May 13, 2010 at 09:31:27AM -0500, Kevin Grittner wrote:
> Ray Stell <stellr@cns.vt.edu> wrote:
> > ,3440,,2010-05-13 09:06:35.734 EDT,4bebf95b.d70,5,2010-05-13
> > 09:06:35 EDT,0,FATAL:  could not restore file "00000002.history"
> > from archive: return code 32512
>  
> Return code 32512?  I think you'd be OK if your recovery script
> returned 1 when it didn't find this file.


Tom wrote last year:

Hmm ... 32512 is 0x7F00, which I think means exit(127), which is
generally what the shell returns when it can't find the program
it's supposed to execute.

> sh: /usr/lib/postgresql/8.2/bin/pg_standby: not found
> sh: /usr/lib/postgresql/8.2/bin/pg_standby: not found
> sh: /usr/lib/postgresql/8.2/bin/pg_standby: not found
> sh: /usr/lib/postgresql/8.2/bin/pg_standby: not found

duh.  measure twice, cut once. 



^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2010-05-13 16:04 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-05-11 13:16 upgrade proc with pitr standby Ray Stell <stellr@cns.vt.edu>
2010-05-11 13:29 ` Devrim GÜNDÜZ <devrim@gunduz.org>
2010-05-13 14:25   ` Ray Stell <stellr@cns.vt.edu>
2010-05-13 14:31     ` Kevin Grittner <Kevin.Grittner@wicourts.gov>
2010-05-13 16:04       ` Ray Stell <stellr@cns.vt.edu>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox