postgresql history and timelines

From: Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: postgresql history and timelines
Date: 2018-11-18 09:29:24
Message-ID: CA+t6e1k+akLVuXUGdw0rCM-W9BttNSOcg+Ytt=weric_FSs3sA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi guys,
Wanted to understand something that isnt clear to me, please correct me if
I'm wrong :

-When we want to recover our database or promote a secondary to be a master
a new time line will be created. A new file will be created in the pg_xlog
directory named '00000TIMELINEID.history'.
-During the daily work, the primary or the secondary shouldnt have a
.history file right ?
-The history file contains only the timeline id and the location to start
from the timeline.
-When using repmgr, after cloning the primary and starting the secondary
the secondary should replay wals from :
1.archives
2.local wals
3.Streaming replication from primary
?

I cloned the primary to the secondary, and when I tried to start the
secondary I got the next message :
LOG: restored log file "000000010000090A00000002" from archive
FATAL: requested timeline 2 is not a child of this server's history
DETAIL: Latest checkpoint is at xx on timeline 1, but in the history of
the requested timeline, the server forked off from that timeline at YY.

So I didnt recover my primary or promoted a secondary so how is it possible
that I have a file from timeline 2 ? Are there other operations that
creates a new timeline ?

Thanks.

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Achilleas Mantzios 2018-11-18 13:38:02 Re: postgresql history and timelines
Previous Message Achilleas Mantzios 2018-11-18 07:03:05 Re: PostgreSQL 10.5 : Logical replication timeout results in PANIC in pg_wal "No space left on device"