Skip site navigation (1) Skip section navigation (2)

Re: Missing timeline history file after execution of pg_upgrade

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alexey Klyukin <alexk(at)hintbits(dot)com>
Cc: christian(dot)echerer(at)manroland-web(dot)com, András Váczi <avandras(at)gmail(dot)com>,"pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Missing timeline history file after execution of pg_upgrade
Date: 2015-05-16 04:40:51
Message-ID: 20150516044051.GB16102@momjian.us (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-admin
On Thu, May 14, 2015 at 10:35:29PM -0400, Bruce Momjian wrote:
> > 
> > Nevertheless, the question is should pg_upgrade move the timeline history file
> > from the old server to the new one, and, to be more specific, are
> > there any cases when
> > moving such file is not recommended?
> 
> Sorry I am just getting to this --- you are right it is a bug.  I was
> unaware that pg_upgrade passed the timeline from the old cluster, but it
> does so when setting the WAL starting address with pg_resetxlog -l,
> which includes the timeline as the first eight hex digits.
> 
> I think there are two options:
> 
> 1)  force pg_resetxlog -l to pass timeline 1
> 2)  create a WAL history file to match the old cluster's timeline (!= 1)
> 
> I don't think we want to be doing #2, so I have developed the attached
> patch for #1, which I should backpatch to 9.4.  Do we store the timeline
> in any user tables that might be transfered?  Anywhere else?

Patch applied and backpatched through 9.0.

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +


In response to

pgsql-admin by date

Next:From: girish R G peetleDate: 2015-05-18 09:17:02
Subject: PostgreSQL pg_dump output reading from named pipe on Windows is giving duplicate dump content
Previous:From: Bruce MomjianDate: 2015-05-15 02:35:29
Subject: Re: Missing timeline history file after execution of pg_upgrade

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group