PG15 removes the input and output directory from the pg regression
test files and moves those files into sql and output directories.
Currently cmake errors when those directories are not present in
PG_SOURCE_DIR. This patch makes those directories optional so cmake
does not fail when PG_SOURCE_DIR contains the checkout of a version
without these directories.
https://github.com/postgres/postgres/commit/d1029bb5https://github.com/postgres/postgres/commit/dc9c3b0f
Upstream added a new regression test for binary compatibility check.
Since we define our own types the test will fail with timescaledb
installed as the test does not expect to see those additional types.
This patch changes our CI to ignore result of type_sanity test.
Currently those are only in REL_XX_STABLE but with release of next minor
version those will enter normal tests as well.
https://github.com/postgres/postgres/commit/cf3d79aa31f
Add a workflow to check that CMake files are correctly formatted as
well as a custom target to format CMake files in the repository. This
commit also runs the formatting on all CMake files in the repository.
Change CI tests to run against pg 11.12, 12.7 and 13.3.
The latest postgres versions adjusts the event_trigger test to
output the list of currently defined event triggers making the
test output different when timescaledb is installed since we
define our own event triggers. Due to this change we have to
ignore the result of this test in our CI.
https://github.com/postgres/postgres/commit/f3c45378
This patch adds a way to check and print a notice message
to a user who wants to drop an access node database.
Since database drop can only be done using different database
connection, this functionality is implemented inside loader
extension.
Functionality of the security labels are used in order to mark
a distributed database and make this information accessible
by other databases in pg_shseclabel table.
This adds a skeleton TimescaleDB foreign data wrapper (FDW) for
scale-out clustering. It currently works as a noop FDW that can be
used for testing, although the intention is to develop it into a
full-blown implementation.
Set random_page_cost to 1.0 to produce more reasonable plans.
This is similar to what timescaledb-tune would set.
This patch also adds test/pgtest.conf which is only used as
postgresql.conf for running the PostgreSQL test suite, because
the random_page_cost change lead to test failures in the PostgreSQL
test suite.
To verify that PostgreSQL operations on regular tables are unaffected by
the TimescaleDB extension, the regular PostgreSQL regression tests can be
run with the TimescaleDB extension loaded.
To enable the build target (`pginstallcheck`), one needs to set the
CMake `PG_SOURCE_DIR` variable to point to the PostgreSQL source code, which
needs to have at least the regression test suite compiled.
The PostgreSQL tests suite will run on every Travis build.