Re: pg_rewind WAL segments deletion pitfall

From: torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>
To: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, michael(at)paquier(dot)xyz, pgsql-hackers(at)postgresql(dot)org, bungina(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_rewind WAL segments deletion pitfall
Date: 2023-10-18 06:50:39
Message-ID: 763cac924055f1669578bea950c667c7@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Thanks for the patch.

I tested the v6 patch using the test script attached on [1], old primary
has succeeded to become new standby.

I have very minor questions on the regression tests mainly regarding the
consistency with other tests for pg_rewind:

> +setup_cluster;
> +create_standby;

Would it be better to add parentheses?
Also should we add "RewindTest::" for these function?

> +primary_psql("create table t(a int)");
> +primary_psql("insert into t values(0)");
> +primary_psql("select pg_switch_wal()");
..

Should 'select', 'create', etc be capitalized?

> my $false = "$^X -e 'exit(1)'";
I feel it's hard to understand what does this mean.
Isn't it better to add comments and describe this is for windows
environments?

--
Regards,

--
Atsushi Torikoshi
NTT DATA Group Corporation

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2023-10-18 06:57:37 Re: Assert failure when CREATE TEMP TABLE
Previous Message Michael Paquier 2023-10-18 01:22:14 Re: BUG #18155: Logical Apply Worker Timeout During TableSync Causes Either Stuckness or Data Loss

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2023-10-18 07:07:38 Re: Rename backup_label to recovery_control
Previous Message Richard Guo 2023-10-18 06:39:41 Re: Oversight in reparameterize_path_by_child leading to executor crash