| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Clécio Anderson <clecioanderson(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_basebackup and timeline issues |
| Date: | 2020-05-20 07:59:52 |
| Message-ID: | 5e7267f0612ff2256abf7883103b605351059aa8.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, 2020-05-19 at 15:02 -0300, Clécio Anderson wrote:
> Sometimes when I need to run pg_basebackup to recreate a slave server I receive the error message below:
> Latest checkpoint is at 427A/6D6743F0 on timeline 2, but in the history of the requested timeline, the server forked off from that timeline at 0/0
> When it happens.. After I edit master's history file pointing to a timeline referenced by the slave's slot I can issue the pg_basebackup without hassle.
> I would like to know If there is any way to ignore or bypass this timeline lookup on master`s history file when issuing pg_basebackup command on slave server.
Not sure, but did you remove any *.history files in the WAL directory?
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Clécio Anderson | 2020-05-20 12:49:47 | Re: pg_basebackup and timeline issues |
| Previous Message | Clécio Anderson | 2020-05-19 18:02:05 | pg_basebackup and timeline issues |