Re: Proposal: remove obsolete hot-standby testing infrastructure - Mailing list pgsql-hackers

From Alexander Lakhin
Subject Re: Proposal: remove obsolete hot-standby testing infrastructure
Date
Msg-id 473567ce-ec6f-416f-fb0c-aba4e5480333@gmail.com
Whole thread Raw
In response to Proposal: remove obsolete hot-standby testing infrastructure  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposal: remove obsolete hot-standby testing infrastructure
List pgsql-hackers
Hello Tom,
04.01.2022 00:50, Tom Lane wrote:
> The attached proposed patch removes some ancient infrastructure for
> manually testing hot standby.  I doubt anyone has used this in years,
> because AFAICS there is nothing here that's not done better by the
> src/test/recovery TAP tests.  (Or if there is, we ought to migrate
> it into the TAP tests.)
>
> Thoughts?
It's hardly that important, but we (Postgres Pro) run this test
regularly to check for primary-standby compatibility. It's useful when
checking binary packages from different minor versions. For example, we
setup postgresql-14.0 and postgresql-14.1 aside (renaming one
installation' directory and changing it's port) and perform the test.
What've found with it was e.g. incompatibility due to linkage of
different libicu versions (that was PgPro-only issue). I don't remember
whether we found something related to PostgreSQL itself, but we
definitely use this test and I'm not sure how to replace it in our setup
with a TAP test. On the other hand, testing binaries is not accustomed
in the community yet, so when such testing will be adopted, probably a
brand new set of tests should emerge.

Best regards,
Alexander



pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: psql - add SHOW_ALL_RESULTS option
Next
From: Stanislav Bashkyrtsev
Date:
Subject: Re: PostgreSQL stops when adding a breakpoint in CLion