Re: In-core regression tests for replication, cascading, archiving, PITR, etc. Michael Paquier

<p dir="ltr"><p dir="ltr">-- <br /> greg<br /> On 5 Jan 2014 14:54, "Mark Dilger" <<a
href="mailto:markdilger@yahoo.com">markdilger@yahoo.com</a>>wrote:<br /> ><br /> > I am building a regression
testsystem for replication and came across<br /> > this email thread.  I have gotten pretty far into my
implementation,but<br /> > would be happy to make modifications if folks have improvements to<br /> > suggest. 
Ifthe community likes my design, or a modified version based<br /> > on your feedback, I'd be happy to submit a
patch.<pdir="ltr">This sounds pretty cool. The real trick will be in testing concurrent behaviour -- I.e. queries on
theslave when it's replaying logs at a certain point. But right now we have nothing so anything would be an
improvement.<br/><p dir="ltr">>  This is possible all on one system because the database clusters<br /> > are
chroot'edto see their own /data directory and not the /data directory<br /> > of the other chroot'ed clusters,
althoughthe rest of the system, like /bin<br /> > and /etc and /dev are all bind mounted and visible to each
cluster.<pdir="ltr">This isn't necessary. You can use the same binaries and run initdb with a different location just
fine.Then start up the database with -D to specify the directory.<br />