From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: In-core regression tests for replication, cascading, archiving, PITR, etc. |
Date: | 2013-12-02 09:24:32 |
Message-ID: | 529C51D0.6050600@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/02/2013 08:40 AM, Michael Paquier wrote:
> The data replication bug causing data corruption on hot slaves found
> lately (http://wiki.postgresql.org/wiki/Nov2013ReplicationIssue) is
> causing a certain amount of damage among the users of Postgres, either
> companies or individuals, and impacts a lot of people. So perhaps it
> would be a good time to start thinking about adding some dedicated
> regression tests for replication, archiving, PITR, data integrity,
> parameter reloading, etc. The possible number of things or use-cases
> that could be applied to that is very vast, but let's say that it
> involves the manipulation of multiple Postgres nodes and structures
> (like a WAL archive) defining a Postgres cluster.
>
> The main purpose of those test would be really simple: using a given
> GIT repository, a buildfarm or developer should be able to run a
> single "make check" command that runs those tests on a local machine
> in a fashion similar to isolation or regression tests and validate
> builds or patches.
+1. The need for such a test suite has been mentioned every single time
that a bug or new feature related to replication, PITR or hot standby
has come up. So yes please! The only thing missing is someone to
actually write the thing. So if you have the time and energy, that'd be
great!
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2013-12-02 09:26:22 | Re: Handling GIN incomplete splits |
Previous Message | Heikki Linnakangas | 2013-12-02 09:07:28 | Re: Extension Templates S03E11 |