Add expected files for regression tests.

Due to compatibility break by the recent PostgreSQL core code changes
we need to split expected files into each minor releases rather than
each major releases.

Now the mapping between PostgreSQL version and expected file is
complicated as follows.

* version 10
  * >= 10.3 : repack_3.out, tablespace_2.out
  * < 10.3 : repack_2.out, tablespace.out

* version 9.6
  * >= 9.6.8 : repack_4.out, tablespace_2.out
  * < 9.6.8 : repack.out, tablespace.out

* version 9.5
  * >= 9.5.12 : repack_4.out, tablespace_2.out
  * < 9.5.12 : repack.out, tablespace_1.out

* version 9.4
  * >= 9.4.17 : repack_5.out, tablespace_2.out
  * < 9.4.17 : repack_1.out, tablespace_1.out

* version 9.3
  * >= 9.3.22 : repack_6.out, tablespace_3.out
  * < 9.3.22 : repack_1.out, tablespace_1.out

* version 9.2 : repack_1.out, tablespace_1.out

* version 9.1 : repack_1.out, tablespace_1.out
This commit is contained in:
Masahiko Sawada
2018-03-09 13:43:04 +09:00
parent a0fe223f8b
commit 64c22ffc5f
10 changed files with 2518 additions and 52 deletions

View File

@ -356,13 +356,16 @@ get_relation_name(Oid relid)
/*
* Relation names given by PostgreSQL core are always
* qualified since some minor releases.
* qualified since some minor releases. Note that this change
* doesn't introduce to PostgreSQL 9.2 and 9.1 releases.
*/
#if ((PG_VERSION_NUM >= 100000 && PG_VERSION_NUM < 100003) || \
(PG_VERSION_NUM >= 90600 && PG_VERSION_NUM < 90608) || \
(PG_VERSION_NUM >= 90500 && PG_VERSION_NUM < 90512) || \
(PG_VERSION_NUM >= 90400 && PG_VERSION_NUM < 90417) || \
(PG_VERSION_NUM >= 90300 && PG_VERSION_NUM < 90322))
(PG_VERSION_NUM >= 90300 && PG_VERSION_NUM < 90322) || \
(PG_VERSION_NUM >= 90200 && PG_VERSION_NUM < 90300) || \
(PG_VERSION_NUM >= 90100 && PG_VERSION_NUM < 90200))
/* Qualify the name if not visible in search path */
if (RelationIsVisible(relid))
nspname = NULL;