18 Commits

Author SHA1 Message Date
Mats Kindahl
10b3da03ec Break out multinode update tests
This commit is part of a longer sequence to refactor the update tests
for use with smoke testing.

The multinode parts of the tests are broken out into a new version to
make the logic simpler.

- All multinode tests are now added to a new version, `v7` which allow
  us to create multinode objects only for versions that support
  multinode.
- Test script `test_updates_pg11` and `test_updates_pg12` are changed
  to use `v6` for updates from versions preceeding 2.0 and `v7` for
  versions 2.0 and later.
- Setup file `post.update.sql` is not needed any more since it was used
  to "fix" a pre-2.0 updated version to add data nodes so that it
  matched the clean setup. This is not necessary any more since v6 does
  not add data nodes for some versions and not for others.
2021-03-04 11:48:49 +01:00
Sven Klemm
22870cfec6 Add 2.1.0 to update test scripts 2021-02-23 17:25:40 +01:00
Sven Klemm
ab736fda90 Add 2.0.2 to update test scripts 2021-02-21 20:13:09 +01:00
Dmitry Simonenko
2fb7034c8f Add 1.7.5 to update test scripts 2021-02-18 15:28:51 +03:00
Sven Klemm
99e450d2a3 Add 2.0.1 to update test scripts 2021-01-28 20:54:02 +01:00
Mats Kindahl
c71632542c Fix repair in update scripts
The commit fixes two bugs in the repair scripts that could
prevent an update in rare circumstances.

For the 1.7.1--1.7.2 repair script: if there were several missing
dimension slices in different hypertables with the same column name,
the repair script would be confused on what constraint had what type
and generate an error.

For the 2.0.0-rc1--2.0.0-rc2 repair script: if a partition constraint
was broken, it would generate an error rather than repairing the
dimension slices because BIGINT_MIN would be cast to a double float and
then an attempt would be made to cast it back to bigint, causing an
overflow error.

This commit also creates an update repair test that breaks a few tables
for pre-2.0 versions to ensure that the repair script actually fixes
them.  The integrity check for the update tests already contain a check
that dimension slices are valid, so there is no need to add a test for
that.

This commit adds an extra dimension in the workflow to test updates
with repair and run that separately. It also changes the update test
scripts to by default run without repair tests and add the additional
option `-r` for running repair tests in addition to the normal tests.

Fixes #2824
2021-01-28 15:04:30 +01:00
Ruslan Fomkin
71633c3388 Add 2.0.0 to update test scripts 2020-12-22 09:23:13 +01:00
Sven Klemm
7eb6a9d752 Add 2.0.0-rc4 to update test scripts 2020-12-17 14:25:33 +01:00
Erik Nordström
acb8732922 Add 2.0.0-rc3 to update tests
Add the latest release candidate to the update tests.
2020-11-16 17:13:29 +01:00
Sven Klemm
374c405db3 Add 2.0.0-rc2 to update tests 2020-10-21 01:30:01 +02:00
Sven Klemm
cc94d56d0e Add 2.0.0-rc1 to update test scripts 2020-10-06 01:50:53 +02:00
Sven Klemm
74b01fbd1b Add 1.7.4 to update test scripts 2020-09-08 20:36:21 +02:00
Sven Klemm
ba93cbf50c Add 1.7.3 to update test scripts 2020-08-27 13:57:22 +02:00
Sven Klemm
41c89b5648 Add 1.7.2 to update test scripts 2020-07-06 17:59:15 +02:00
gayyappan
b93b30b0c2 Add counts to compression statistics
Store information related to compressed and uncompressed row
counts after compressing a chunk. This is saved in
compression_chunk_size table.
2020-06-19 15:58:04 -04:00
Sven Klemm
c90397fd6a Remove support for PG9.6 and PG10
This patch removes code support for PG9.6 and PG10. In addition to
removing PG96 and PG10 macros the following changes are done:

remove HAVE_INT64_TIMESTAMP since this is always true on PG10+
remove PG_VERSION_SUPPORTS_MULTINODE
2020-06-02 23:48:35 +02:00
Sven Klemm
1df97acfd2 Add 1.7.1 to update test scripts 2020-05-19 15:00:16 +02:00
Sven Klemm
5a6fd603e6 Add 1.7.0 to update test scripts
Due to the changes of the default view behaviour of continuous
aggregates we need a new testsuite for the update tests for 1.7.0

This patch also changes the update test for 9.6 and 10 to run on
cron and 11 and 12 on pull request.
2020-04-21 01:39:00 +02:00