table_views ... ok
test sanity_check ... ok
test errors ... ok
test select ... ok
parallel group (20 tests): select_into select_distinct select_distinct_on select_implicit select_having subselect case aggregates transactions hash_index delete random portals arrays namespace update union btree_index join prepared_xacts
select_into ... ok
select_distinct ... ok
select_distinct_on ... ok
select_implicit ... ok
select_having ... ok
subselect ... ok
union ... ok
case ... ok
join ... ok
aggregates ... ok
transactions ... ok
random ... ok
portals ... ok
arrays ... ok
btree_index ... ok
hash_index ... ok
update ... ok
namespace ... ok
prepared_xacts ... ok
delete ... ok
parallel group (4 tests): security_label privileges matview collate
privileges ... ok
security_label ... ok
collate ... ok
matview ... ok
parallel group (3 tests): psql alter_generic misc
alter_generic ... ok
misc ... ok
psql ... ok
test rules ... ok
test event_trigger ... ok
parallel group (16 tests): select_views portals_p2 dependency foreign_key guc tsearch advisory_lock cluster bitmapops combocid functional_deps xmlmap tsdicts foreign_data json window
select_views ... ok
portals_p2 ... ok
foreign_key ... ok
cluster ... ok
dependency ... ok
guc ... ok
bitmapops ... ok
combocid ... ok
tsearch ... ok
tsdicts ... ok
foreign_data ... ok
window ... ok
xmlmap ... ok
functional_deps ... ok
advisory_lock ... ok
json ... ok
parallel group (19 tests): limit copy2 prepare truncate xml domain returning without_oid rowtypes with largeobject alter_table rangefuncs polymorphism temp plancache sequence conversion plpgsql
plancache ... ok
limit ... ok
plpgsql ... ok
copy2 ... ok
temp ... ok
domain ... ok
rangefuncs ... ok
prepare ... ok
without_oid ... ok
conversion ... ok
truncate ... ok
alter_table ... ok
sequence ... ok
polymorphism ... ok
rowtypes ... ok
returning ... ok
largeobject ... ok
with ... ok
xml ... ok
test stats ... ok
============== shutting down postmaster ==============
=======================
All 136 tests passed.
=======================
?
通过上面的例子可以看出来，regress test的测试用例使用起来是相当的简单。下面我们来详细介绍下regress test。
?
2. 启动regress test
通过上面的例子，我们看出启动regress test是很容易的，只要在src/test/regress目录下执行make check即可。
?
3. 测试模式
例子中的执行语句如下：
../../../src/test/regress/pg_regress--inputdir=. --temp-install=./tmp_check --top-builddir=../../.. --dlpath=. --schedule=./parallel_schedule
这个--schedule=./parallel_schedule参数是什么意思呢？这是因为在PG/PGXC的regress test中，有两种测试模式，分别为：基于临时安装的数据库测试和基于已安装的数据库进行测试。两者的区别在于，临时安装的测试在测试开始之前会自行安装数据库集群，测试完成之后会将数据库集群停掉，并删除临时产物。反之则是基于已安装的集群。这就是临时安装的log：
?
../../../src/test/regress/pg_regress --inputdir=. --temp-install=./tmp_check --top-builddir=../../.. --dlpath=. --schedule=./parallel_schedule
============== creating temporary installation ==============
============== initializing database system ==============
============== starting postmaster ==============
running on port 57536 with PID 2843
基于已安装的数据库进行测试的方法如下：
?
?
[postgres@gorilla1 regress]$ gmake installcheck
gmake -C ../../../src/port all
gmake[1]: Entering directory `/tmp/postgresql-9.3.4/src/port'
gmake -C ../backend submake-errcodes
gmake[2]: Entering directory `/tmp/postgresql-9.3.4/src/backend'
gmake[2]: Nothing to b