Commit Graph

471 Commits

Author SHA1 Message Date
ce8e283f63 Merge branch 'clean-tests' 2018-03-20 12:56:25 +00:00
73851d2e5c Test file separated in setup - run - check
The run part has different output across minor versions, the others not.

Dropped test files identification statement as now the variable part is
in small chunks.
2018-03-20 12:49:15 +00:00
74d56ef4d6 Dropped now equivalent test output files 2018-03-20 12:31:39 +00:00
a5509c7415 No superuser check separated from other tests
The output differs across versions because it can include the context.

This made:

- repack.out = repack_1.out
- repack_3.out = repack_5.out
2018-03-20 12:29:16 +00:00
6dfbfffe59 Dropped duplicate test output files 2018-03-20 12:20:06 +00:00
0cb08e5512 Variable psql table output moved in separate file
This made:

- repack.out == repack_2.out
- repack_3.out == repack_4.out
- repack_1.out == repack_6.out
2018-03-20 11:39:41 +00:00
31d15a87e7 Merge branch 'schema_qualified' 2018-03-19 19:47:23 +00:00
c62d865c18 Choose schema name visibility from running server version
Guarantee the extension compiled on newer servers can be used on older
ones.
2018-03-19 19:41:46 +00:00
07e944d9d1 Use the Postgres way to get the version number
Unsurprisingly, there was one.
2018-03-19 19:07:33 +00:00
e499d3df10 Merge branch 'schema_qualified' 2018-03-09 16:13:51 +00:00
2fd0eb050a A more compact way to verify the identity of the test files 2018-03-09 15:32:26 +00:00
64c22ffc5f 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
2018-03-09 14:00:04 +09:00
a0fe223f8b Forgot to add expected files of regression tests. 2018-03-09 11:00:42 +09:00
2f6196d654 Always qualify relation names.
Due to change at PostgreSQL 10.3, 9.6.8, 9.5.12, 9.4.17 and 9.3.22,
relation names passed by PostgreSQL function such as
pg_get_indexdef_string() are schema-qualified, which could be cause
of a parse error.
2018-03-09 10:53:43 +09:00
bf61feefc4 Fix Japanese doc. 2017-10-17 12:16:44 +09:00
4fa4f8945e Fix change logs of version 1.4.1 and 1.4.2. 2017-10-17 12:11:28 +09:00
fdad0b87a2 Fix Japanese doc. 2017-10-17 18:03:07 +09:00
7166a0ee8c Preparing release 1.4.2 2017-10-13 09:16:37 +01:00
4b86bb1c41 Merge pull request #150 from MasahikoSawada/fix_regress_test
Change to use only the characters that are printable ASCII.
2017-10-04 11:05:53 +09:00
f690ada80f Change to use only the characters that are printable ASCII.
The regression test could fail on some environments such as where
the encoding is SQL_ASCII.

Fixed issue #130.
2017-10-03 11:51:07 -07:00
f83cb2a6e0 Merge pull request #149 from craigds/patch-1
Clarify note about GiST indexes
2017-10-03 08:48:08 -04:00
f789bc965d Clarify note about GiST indexes
As per http://lists.pgfoundry.org/pipermail/reorg-general/2015-May/000306.html
2017-09-29 14:03:02 +13:00
66f5da58c9 Update Japanese doc for the recent changes. 2017-09-25 11:19:22 -07:00
1cb3a52ccb Changelog updated with last developments 2017-09-25 03:17:00 +01:00
d7b4e75c10 PG 10 expected test result fixed with changes added in 1.4.1 2017-09-25 02:53:11 +01:00
7413a65985 Merge remote-tracking branch 'origin/master' into pg10 2017-09-25 02:45:49 +01:00
9e4dd00415 Dropped compiler warning
Probably only raised compiling on 32 bits platforms.
2017-09-25 02:37:29 +01:00
f996fd8fb3 Allow building with PostgreSQL 10rc1
This is what we get:

    $ pg_config --version
    PostgreSQL 10rc1
2017-09-25 02:33:13 +01:00
b2d470a122 Merge pull request #143 from MasahikoSawada/fix_lock_exclusive
Reset the transcation state before exiting from lock_exclusive.
2017-08-24 09:20:08 +09:00
900bb8369b Reset the transcation state before exiting from lock_exclusive.
Previously we exited from lock_exclusive() while opening the
transaction that started at beggning if --no-kill-backend option
is specified. This caused that DROP INDEX CONCURRENTLY fails
because it cannot be executed within a user transaction block.

Fixed issue #129.
2017-08-18 15:25:04 +09:00
1b651bd3d9 Avoid return from lock_exclusive() while in transaction ..
..causing "ERROR: DROP INDEX CONCURRENTLY cannot run inside a transaction block"
github#129
2017-08-18 15:21:09 +09:00
20f5bf4878 Update pg_repack_jp.rst for release 1.4.1. 2017-08-13 00:32:13 +09:00
ea27a94578 Typo fixed (after releasing, of course...) 2017-08-12 13:15:14 +01:00
b2be4741c9 Preparing release 1.4.1 2017-08-12 12:56:43 +01:00
766937ab4c Merge pull request #140 from MasahikoSawada/fix_order
Fix reorganize table without sorting.
2017-08-12 13:25:16 +09:00
34e71adbbd Fix a typo in pg_repack.c file. 2017-08-05 20:16:31 +09:00
f8ba09fd31 Get rid of unnecessary lines in expected file. 2017-08-05 02:49:56 +09:00
33f4c30563 Fix reorganize table without sorting.
Commit 5adff6ff0b separated the
data copy from creating table. This is a cause of bug that
pg_repack doesn't actually sort table during reorganization.
This commit fixes this issue by adding ORDER BY clause to Copy
SQL rather than CREATE TABLE SQL.

Reported by acmzero on issue #138.
2017-08-05 02:31:47 +09:00
cac8179299 Merge pull request #136 from MasahikoSawada/fix_memory_leak
Fix a small memory leak in repack_one_database function.
2017-07-13 19:26:27 +09:00
c2ed98a85b Fix a small memory leak in repack_one_database function.
Noticed by coverity scan.
2017-07-12 17:04:33 -07:00
cbb3b7f916 Minimum postgres version supported fixed in META.json 2017-04-26 11:30:02 +01:00
5b1001d620 Fixed info to refresh website, suggest to tag after deployment 2017-04-25 17:58:09 +01:00
2d11efea18 Fixed reST error in Japanese docs 2017-04-25 16:13:53 +01:00
910d5fd86a Fixed version number
1.4 would have been good for me too... But semver requires 1.4.0
2017-04-25 16:11:27 +01:00
a7e0b6748e Added identifier to recognize the test output file 2017-04-25 15:50:33 +01:00
8bdba99642 Fixed hba configuration to test on PG 10
Use env vars instead of hardcoded PG version to select config options.
2017-04-25 15:09:43 +01:00
a5a5f3447a Added expected test for postgres 10
The \d output format changed
2017-04-25 15:09:27 +01:00
773dc5349d Work around CatalogIndexInsert no more exported in PG 10
The CatalogTupleUpdateWithInfo performs the two operation
simple_heap_update and CatalogIndexInsert.
2017-04-25 15:09:27 +01:00
19e34a3202 Added PG 10 compatibility wrapper to simple_prompt()
Also checking for malloc failure into previous version's simple_prompt()
calls.
2017-04-25 15:09:27 +01:00
b9b8e60bda Set up travis tests to run with postgres 10 2017-04-25 15:09:27 +01:00