The GITHUB_TOKEN variable is getting overwritten with the Github Actions
token.
Moreover, the token-based remote's credentials are somehow overwritten
on push with credentials used for checkout action. Use the PAT for it as
well.
This should finally let the backport script to update the outstanding
backport PRs to the current target branch, and workflows to start for
them.
Disable-check: force-changelog-file
Disable-check: approval-count
This will help update the pending backport PR to the latest version of
the release branch.
GitHub doesn't provide a built-in possibility to trigger a workflow on
the main branch when another branch has changed. For example, if we had
a "push: ?.*.x" condition, it would trigger the backport workflow on the
release branch itself, which is not what we need. So we have to use a
helper workflow instead.
Add support for running VectorAgg on top of scans on Hypercore
TAM. Currently, only ColumnarScan can run below VectorAgg when
Hypercore TAM is used. In theory, a SeqScan or IndexScan reading from
Hypercore TAM should also work because they would produce Arrow
slots. However, only ColumnarScan performs vectorized filtering, which
is currently assumed to happen before the VectorAgg node.
In ColumnarScan, it is necessary to turn off projection when VectorAgg
is used. Otherwise, it would project the arrow slot into a virtual
slot, thus losing the vector data. Ideally, a projection should never
be planned to begin with, but this isn't possible since VectorAgg
modifies existing non-vectorized Agg plans that already includes
projections.
For the remaining nightly runs.
Remove reference to non-existent trigger/homebrew_test branch.
---------
Signed-off-by: Pallavi Sontakke <pallavi@timescale.com>
Co-authored-by: Philip Krauss <35487337+philkra@users.noreply.github.com>
Since we depend on the openssl version of the postgres installer
to match the openssl version we built against and we can't ensure
stability of that version in the postgres installer we only test
windows package against the latest available postgres version.
with GitHub workflow files.
We run these steps for a new minor version - feature freeze :
- create the Bump-version PR on `main`,
- create the new minor-version-branch , e.g. `2.18.x`
- create the Release PR on minor-version-branch
We no more use a fork, but a branch directly.
To detect the problematic patterns that were part of the 2.18 release
we can check the sql scripts against a list of allowed statements.
Any non idempotent operation should be in the pre_install scripts
and not the scripts that get appended for the update scripts.
This patch adjusts the downgrade script generation to not include
incompatible files from the 2.18.0 release that would break script
generation and replaces them with a working version. This adjustment
can be removed after we release of 2.18.1.
This patch also reenables the downgrade test.
The 2.18.0 sql files for building downgrade scripts have some
incompatible changes in them that prevent downgrade script generation.
This patch disable downgrade test until the necessary adjustments
in downgrade script generation are made.
If the scheduler receives an error, it will never restart again since
`bgw_restart_time` is set to `BGW_NEVER_RESTART`, which will prevent
all jobs from executing.
This commit adds the GUC `timescaledb.bgw_scheduler_restart_time` that
can be set to the restart time for the scheduler. It defaults
to 60 seconds, which is the default restart interval for background
workers defined by PostgreSQL.
It also adds `timescaledb.debug_bgw_scheduler_exit_status` to be able
to shutdown the scheduler with a non-zero exit status, which allows the
restart functionality to be tested.
It also ensures that `backend_type` is explicitly set up rather than
copied from `application_name` and add some more information to
`application_name`. It also updates the tests to use `backend_type`
where applicable.
To avoid exhausting slots when the launcher restarts, it will kill all
existing schedulers and start new ones. Since background worker slots
are easily exhausted in the `bgw_launcher` test, we do not run it
repeatedly in the flakes workflow.
Bitnami removed support for LTS branches. For us this means only
PG17 will get postgres version updates. So this PR removes the
images for previous branches from CI test.
https://github.com/bitnami/containers/issues/75671
This patch also adds missing timescaledb-ha:pg17 image to the tests.
In some places we didn't pass the top-level config overrides to the
lowest level debug config builder, which can result in config values
being overwritten in an unexpected ways.
GitHub Actions using `ubuntu-latest` have been changed to use
`ubuntu-24.04` instead by default
(https://github.com/actions/runner-images/issues/10636) which breaks our
APT-ARM64 package workflow. This pins the version back to `ubuntu-22.04`
to avoid this.
Disable-check: force-changelog-file
This adds a test to check the ABI compatibility with PG snapshot.
Timescaledb is built against the mininum abi version of postgres
supported, for each major version of PG and tested against the latest
snapshot.
Disable-check: force-changelog-file
Remove event information from workflow and count the number of files
rather than try to test for them. Also include approvers that have
"NONE" as author status.
Versions of the extension cannot be expected to always work in the
backwards direction so we cannot reliably test that builds against
later versions of PostgreSQL (e.g., 17.3) work with earlier versions
(e.g., 17.0) if new functions are introduced in the later version.
