Re: how to identify the timeline of specified recovery_target_timewhen do multiple PITR
От | Laurenz Albe |
---|---|
Тема | Re: how to identify the timeline of specified recovery_target_timewhen do multiple PITR |
Дата | |
Msg-id | 34d85bfc77e9a63890e28ea13953c30508233469.camel@cybertec.at обсуждение исходный текст |
Ответ на | Re: how to identify the timeline of specified recovery_target_timewhen do multiple PITR (magodo <wztdyl@sina.com>) |
Ответы |
Re: how to identify the timeline of specified recovery_target_timewhen do multiple PITR
|
Список | pgsql-general |
magodo wrote: > > By default, recovery will stay on the timeline where it started. > > If you want to go to timeline 2 or 3, you have to specify > > recovery_target_timeline. > > > For me, the specified point corresponds to timeline 1, because at that > time, the timeline is 1 indeed (when there is no timeline 2 branched > out yet). > > So in other word, my expectation is like I want to get the first > timeline which covers the specified time. > > As you mentioned, there is no active timeline concept in postgres, then > what is the best practice to meet my expectation? Do I have to somehow > record the timestamp when archived wal's timeline has been changed, > then compare the specified recovery target time with those records to > find the first timeline which covers that time? As I wrote, that is the default behavior; PostgreSQL will stay on the timeline that was active when recovery was started. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com
В списке pgsql-general по дате отправления: