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

From: Soumyadeep Chakraborty <soumyadeep2007(at)gmail(dot)com>
To: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
Cc: pgsql-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 07:51:52
Message-ID: CAE-ML+-FK1c=Q=J7_kzrTuZ9OjMbz=9eE8EDYsOZxOky6hmruQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 6, 2023 at 11:33 PM Alexander Kukushkin <cyberdemn(at)gmail(dot)com> wrote:
>
>
> Lets assume that on the source we have "pg_log" and on the target we have "my_log" (they are configured using "log_directory" GUC).
> When doing rewind in this case we want neither to remove the content of "my_log" on the target nor to copy content of "pg_log" from the source.
> It couldn't be achieved just by introducing a static string "log". The "log_directory" GUC must be examined on both, source and target.

Trouble with doing that is if pg_rewind is run in non-libpq (offline)
mode. Then we would have to parse it out of the conf file(s)?
Is there a standard way of doing that?

Regards,
Soumyadeep (VMware)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2023-03-07 07:55:04 RE: Rework LogicalOutputPluginWriterUpdateProgress
Previous Message Peter Smith 2023-03-07 07:48:57 Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher