Re: pg_rewind with cascade standby doesn't work well - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: pg_rewind with cascade standby doesn't work well
Date
Msg-id CAJ7c6TPwU22RkRUot2FbjRoAK1hPxg+RcCnsFdB_b-CwOTrnCw@mail.gmail.com
Whole thread Raw
In response to Re: pg_rewind with cascade standby doesn't work well  (Kuwamura Masaki <kuwamura@db.is.i.nagoya-u.ac.jp>)
Responses Re: pg_rewind with cascade standby doesn't work well
List pgsql-hackers
Hi,

> >> IMO a test is needed that makes sure no one is going to break this in
> >> the future.
> >
> > You definitely need more complex test scenarios for that.  If you can
> > come up with new ways to make the TAP tests of pg_rewind mode modular
> > in handling more complicated node setups, that would be a nice
> > addition, for example.
>
> I'm sorry for lacking tests. For now, I started off with a simple test
> that cause the problem I mentioned. The updated WIP patch 0001 includes
> the new test for pg_rewind.

Many thanks for a quick update.

> And also, I'm afraid that I'm not sure what kind of tests I have to make
> for fix this behavior. Would you mind giving me some advice?

Personally I would prefer not to increase the scope of work. Your TAP
test added in 0001 seems to be adequate.

> BTW, I was able to
> reproduce the assertion failure Kuwamura-san reported, even after applying
> your latest patch from the thread.

Do you mean that the test fails or it doesn't but there are other
steps to reproduce the issue?

-- 
Best regards,
Aleksander Alekseev



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: XLog size reductions: smaller XLRec block header for PG17
Next
From: Greg Sabino Mullane
Date:
Subject: Re: [PATCH] Add inline comments to the pg_hba_file_rules view