Skip to content

Conversation

dpxcc
Copy link
Contributor

@dpxcc dpxcc commented Aug 19, 2025

Problem

Upgrade pg_mooncake to v0.2-poc-2025.08.25

Summary of changes

In this build, pg_mooncake connects to a remote moonlink service with prepopulated tables, and runs a custom scan on those tables using pg_duckdb/DuckDB

@dpxcc dpxcc requested a review from a team as a code owner August 19, 2025 22:54
@dpxcc dpxcc requested review from ololobus and MMeent August 19, 2025 22:54
@github-actions github-actions bot added the external A PR or Issue is created by an external user label Aug 19, 2025
Copy link
Contributor Author

@dpxcc dpxcc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to add pg_mooncake to shared_preload_libraries
Where’s the right place to enable that?
I didn’t see how it was being set for pg_duckdb

WORKDIR /ext-src/pg_duckdb-src
RUN make install -j $(getconf _NPROCESSORS_ONLN) && \
echo 'trusted = true' >> /usr/local/pgsql/share/extension/pg_duckdb.control
# FROM build-deps AS pg_duckdb-src
Copy link
Contributor Author

@dpxcc dpxcc Aug 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I temporarily disabled pg_duckdb for this POC build to avoid conflicts

We are working on making pg_mooncake a subextension of pg_duckdb. Once pg_mooncake v0.2 is officially released, we will be fully compatible with pg_duckdb

@kelvich kelvich added the approved-for-ci-run Changes are safe to trigger CI for the PR label Aug 19, 2025
@github-actions github-actions bot removed the approved-for-ci-run Changes are safe to trigger CI for the PR label Aug 19, 2025
@vipvap vipvap mentioned this pull request Aug 19, 2025
Copy link

github-actions bot commented Aug 20, 2025

9119 tests run: 8400 passed, 66 failed, 653 skipped (full report)


Failures on Postgres 17

Failures on Postgres 16

Failures on Postgres 15

Failures on Postgres 14

# Run all failed tests locally:
scripts/pytest -vv -n $(nproc) -k "test_backward_compatibility[release-pg14] or test_backward_compatibility[release-pg14] or test_versions_mismatch[release-pg14-combination_nnnnn] or test_versions_mismatch[release-pg14-combination_nnnnn] or test_versions_mismatch[release-pg14-combination_ooonn] or test_versions_mismatch[release-pg14-combination_ooonn] or test_versions_mismatch[release-pg14-combination_ononn] or test_versions_mismatch[release-pg14-combination_ononn] or test_versions_mismatch[release-pg14-combination_onnnn] or test_versions_mismatch[release-pg14-combination_onnnn] or test_versions_mismatch[release-pg14-combination_nnnoo] or test_versions_mismatch[release-pg14-combination_nnnoo] or test_backward_compatibility[release-pg15] or test_backward_compatibility[release-pg15] or test_versions_mismatch[release-pg15-combination_nnnnn] or test_versions_mismatch[release-pg15-combination_nnnnn] or test_versions_mismatch[release-pg15-combination_ooonn] or test_versions_mismatch[release-pg15-combination_ooonn] or test_versions_mismatch[release-pg15-combination_ononn] or test_versions_mismatch[release-pg15-combination_ononn] or test_versions_mismatch[release-pg15-combination_onnnn] or test_versions_mismatch[release-pg15-combination_onnnn] or test_versions_mismatch[release-pg15-combination_nnnoo] or test_versions_mismatch[release-pg15-combination_nnnoo] or test_backward_compatibility[release-pg16] or test_backward_compatibility[release-pg16] or test_versions_mismatch[release-pg16-combination_nnnnn] or test_versions_mismatch[release-pg16-combination_nnnnn] or test_versions_mismatch[release-pg16-combination_ooonn] or test_versions_mismatch[release-pg16-combination_ooonn] or test_versions_mismatch[release-pg16-combination_ononn] or test_versions_mismatch[release-pg16-combination_ononn] or test_versions_mismatch[release-pg16-combination_onnnn] or test_versions_mismatch[release-pg16-combination_onnnn] or test_versions_mismatch[release-pg16-combination_nnnoo] or test_versions_mismatch[release-pg16-combination_nnnoo] or test_backward_compatibility[release-pg17] or test_backward_compatibility[release-pg17] or test_backward_compatibility[debug-pg17] or test_backward_compatibility[release-pg17] or test_backward_compatibility[release-pg17] or test_versions_mismatch[release-pg17-combination_nnnnn] or test_versions_mismatch[release-pg17-combination_nnnnn] or test_versions_mismatch[debug-pg17-combination_nnnnn] or test_versions_mismatch[release-pg17-combination_nnnnn] or test_versions_mismatch[release-pg17-combination_nnnnn] or test_versions_mismatch[release-pg17-combination_ooonn] or test_versions_mismatch[release-pg17-combination_ooonn] or test_versions_mismatch[debug-pg17-combination_ooonn] or test_versions_mismatch[release-pg17-combination_ooonn] or test_versions_mismatch[release-pg17-combination_ooonn] or test_versions_mismatch[release-pg17-combination_ononn] or test_versions_mismatch[release-pg17-combination_ononn] or test_versions_mismatch[debug-pg17-combination_ononn] or test_versions_mismatch[release-pg17-combination_ononn] or test_versions_mismatch[release-pg17-combination_ononn] or test_versions_mismatch[release-pg17-combination_onnnn] or test_versions_mismatch[release-pg17-combination_onnnn] or test_versions_mismatch[debug-pg17-combination_onnnn] or test_versions_mismatch[release-pg17-combination_onnnn] or test_versions_mismatch[release-pg17-combination_onnnn] or test_versions_mismatch[release-pg17-combination_nnnoo] or test_versions_mismatch[release-pg17-combination_nnnoo] or test_versions_mismatch[debug-pg17-combination_nnnoo] or test_versions_mismatch[release-pg17-combination_nnnoo] or test_versions_mismatch[release-pg17-combination_nnnoo]"
Flaky tests (1)

Postgres 16

Test coverage report is not available

The comment gets automatically updated with the latest test results
cfdd35c at 2025-09-02T19:49:57.543Z :recycle:

@kelvich kelvich added the approved-for-ci-run Changes are safe to trigger CI for the PR label Aug 20, 2025
@github-actions github-actions bot removed the approved-for-ci-run Changes are safe to trigger CI for the PR label Aug 20, 2025
@kelvich kelvich added the approved-for-ci-run Changes are safe to trigger CI for the PR label Aug 20, 2025
@github-actions github-actions bot removed the approved-for-ci-run Changes are safe to trigger CI for the PR label Aug 20, 2025
@ololobus ololobus added the approved-for-ci-run Changes are safe to trigger CI for the PR label Aug 22, 2025
@github-actions github-actions bot removed the approved-for-ci-run Changes are safe to trigger CI for the PR label Aug 22, 2025
@dpxcc
Copy link
Contributor Author

dpxcc commented Aug 23, 2025

Could someone please approve the CI to kick off the builds? Thank you! cc: @kelvich

@kelvich kelvich added the approved-for-ci-run Changes are safe to trigger CI for the PR label Aug 24, 2025
@kelvich
Copy link
Contributor

kelvich commented Aug 24, 2025

added label

@github-actions github-actions bot removed the approved-for-ci-run Changes are safe to trigger CI for the PR label Aug 24, 2025
@bayandin bayandin added the approved-for-ci-run Changes are safe to trigger CI for the PR label Sep 2, 2025
@github-actions github-actions bot removed the approved-for-ci-run Changes are safe to trigger CI for the PR label Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external A PR or Issue is created by an external user
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants