Re: pg_rewind: Skip log directory for file type check like pg_wal

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
Cc: Soumyadeep Chakraborty <soumyadeep2007(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_rewind: Skip log directory for file type check like pg_wal
Date: 2023-03-07 09:28:37
Message-ID: DC3F7C53-C8EF-4803-B70A-0AFB2FBFD0C3@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 7 Mar 2023, at 08:33, Alexander Kukushkin <cyberdemn(at)gmail(dot)com> wrote:

> The "log_directory" GUC must be examined on both, source and target.

Agreed, log_directory must be resolved to the configured values. Teaching
pg_rewind about those in case they are stored in $PGDATA sounds like a good
idea though.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2023-03-07 09:30:20 Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
Previous Message Daniel Gustafsson 2023-03-07 09:09:23 Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)