Run the "tablespace" regression test first not last. The former placement
renders useless one of the few test methodologies we have for WAL replay,
which is to intentionally crash the system just after completing the
regression tests and see if it recovers to the expected database state.
The reason is that DROP TABLESPACE forces a checkpoint, so there's essentially
no WAL available for replay after the tests complete.
parallel_schedule (r1.56 -> r1.57)
serial_schedule (r1.53 -> r1.54)
pgsql-committers by date
|Next:||From: Heikki Linnakangas||Date: 2009-08-24 05:39:45|
|Subject: Re: pgsql: Fix a violation of WAL coding rules in the
recent patch to|
|Previous:||From: Tom Lane||Date: 2009-08-24 02:18:40|
|Subject: pgsql: Fix a violation of WAL coding rules in the recent patch to |