Re: Missing timeline history file after execution of pg_upgrade - Mailing list pgsql-admin

From Bruce Momjian
Subject Re: Missing timeline history file after execution of pg_upgrade
Date
Msg-id 20150516044051.GB16102@momjian.us
Whole thread Raw
In response to Re: Missing timeline history file after execution of pg_upgrade  (Bruce Momjian <bruce@momjian.us>)
List 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@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +


pgsql-admin by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Missing timeline history file after execution of pg_upgrade
Next
From: girish R G peetle
Date:
Subject: PostgreSQL pg_dump output reading from named pipe on Windows is giving duplicate dump content