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@xxxxxxxxxx> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
