Skip to content

Keep temp reloid for columnar cases (Backport #8235 to release-12.1)#8328

Merged
ihalatci merged 3 commits into
citusdata:release-12.1from
manaldush:release-12.1_8235
Jun 30, 2026
Merged

Keep temp reloid for columnar cases (Backport #8235 to release-12.1)#8328
ihalatci merged 3 commits into
citusdata:release-12.1from
manaldush:release-12.1_8235

Conversation

@manaldush

Copy link
Copy Markdown
Contributor

Backporting #8235 to release-12.1

PG18 and PG latest minors ignore temporary relations in RelidByRelfilenumber (RelidByRelfilenode in PG15) Relevant PG commit:
postgres/postgres@86831952

Here we are keeping temp reloids instead of getting it with RelidByRelfilenumber, for example, in some cases, we can directly get reloid from relations, in other cases we keep it in some structures.

Note: there is still an outstanding issue with columnar temp tables in concurrent sessions, that will be fixed in PR
#8252

(cherry picked from commit daa69be)

DESCRIPTION: PR description that will go into the change log, up to 78 characters

Backporting citusdata#8235

PG18 and PG latest minors ignore temporary relations in
`RelidByRelfilenumber` (`RelidByRelfilenode` in PG15)
Relevant PG commit:
postgres/postgres@86831952

Here we are keeping temp reloids instead of getting it with
RelidByRelfilenumber, for example, in some cases, we can directly get
reloid from relations, in other cases we keep it in some structures.

Note: there is still an outstanding issue with columnar temp tables in
concurrent sessions, that will be fixed in PR
citusdata#8252

(cherry picked from commit daa69be)
@manaldush manaldush changed the title Keep temp reloid for columnar cases (Backport #8235) Keep temp reloid for columnar cases (Backport #8235 to release-12.1) Nov 7, 2025
@ihalatci ihalatci added this to the 12.1.13 milestone Jun 29, 2026
ihalatci added a commit that referenced this pull request Jun 30, 2026
…1) (#8629)

## Problem
The 1ES self-hosted pool (`1es-gha-citusdata-pool`) is no longer
dispatching jobs, so the **required** `check-arbitrary-configs` jobs sit
`QUEUED` indefinitely. This blocks **every** open release-12.1 PR
(#8519, #8328, #8306, #8626, #8627) from merging despite all other
required checks passing.

## Fix
Flip the `test-arbitrary-configs` job's `runs-on` from the dead
self-hosted 1ES pool to `ubuntu-latest` — a one-line backport of the
config already shipping on `main`.

## Why it is safe
- `main` already runs this exact job/suite/container on `ubuntu-latest`.
- Required-check **names** (`PG14 - check-arbitrary-configs-0`, ...)
derive from the job `name:`, not `runs-on`, so branch protection is
unaffected.
- AC was the **only** job still pinned to the self-hosted pool;
everything else already runs github-hosted.

## Rollout
Merge this first, then "Update branch" on the 5 open PRs so they inherit
the fix and their AC checks run on github-hosted runners.

Unblocks the release-12.1 serial-merge queue.

Co-authored-by: Ibrahim Halatci <ihalatci@microsoft.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@ihalatci ihalatci merged commit 99d4253 into citusdata:release-12.1 Jun 30, 2026
209 of 210 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants