| From: | Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de> |
|---|---|
| To: | Alexander Kukushkin <cyberdemn(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Concurrency issue in pg_rewind |
| Date: | 2020-09-17 08:20:16 |
| Message-ID: | CACACo5RkdXNBNWH_-GLjtN3UwF6rT1wDz0Xw+Hy6zp-JEBMUwA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 16, 2020 at 2:55 PM Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
wrote:
>
> The second time pg_rewind also failed, but the error looked differently:
> servers diverged at WAL location A76/39E55338 on timeline 132
> rewinding from last common checkpoint at A76/1EF254B8 on timeline 132
>
> could not remove file
>
> "/home/postgres/pgdata/pgroot/data/pg_wal/.wal-g/prefetch/running/0000008400000A7600000024":
>
Ouch. I think pg_rewind shouldn't try to remove any random files in pg_wal
that it doesn't know about.
What if the administrator made a backup of some WAL segments there?
--
Alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ajin Cherian | 2020-09-17 08:31:57 | Re: [HACKERS] logical decoding of two-phase transactions |
| Previous Message | Daniel Gustafsson | 2020-09-17 08:15:30 | Re: pgindent vs dtrace on macos |