| From: | Олег Самойлов <splarv(at)ya(dot)ru> |
|---|---|
| To: | Yuri Kanivetsky <yuri(dot)kanivetsky(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: New timeline when starting with a restored data dir |
| Date: | 2019-04-10 15:07:21 |
| Message-ID: | CC5734C0-C33B-4F64-8F58-0BEF9AC59E3B@ya.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
It’s normal behaviour to create a new timeline, when a PostgreSQL slave become a new master. This is for what timelines were designed.
> 19 нояб. 2018 г., в 0:50, Yuri Kanivetsky <yuri(dot)kanivetsky(at)gmail(dot)com> написал(а):
>
> Hi,
>
> I'm trying to set up Barman, and I've noticed that PostgreSQL 10
> creates a new timeline when starting with a restored data dir.
> Particularly, when WAL files are delivered via restore_command. When
> WAL files are copied to pg_wal dir, no new timeline is created. Is it
> to be expected? Can you explain?
>
> I decided to ask here first, since you might know better how
> PostgreSQL operates.
>
> Thanks in advance.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Олег Самойлов | 2019-04-10 15:19:53 | Re: Invoking user of the function with SECURITY DEFINER |
| Previous Message | Олег Самойлов | 2019-04-10 14:16:32 | Re: Performance of ByteA: ascii vs binary |