-
Notifications
You must be signed in to change notification settings - Fork 439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NOAI #9084
NOAI #9084
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
works with my testing
3804a1c
to
9eb7ce0
Compare
Can we add a test to the test suite, please? |
196d804
to
205c4f3
Compare
I've updated the test that checks compatibility with unlogged tables, would that be sufficient? |
5029 tests run: 4865 passed, 0 failed, 164 skipped (full report)Flaky tests (4)Postgres 17
Postgres 16
Postgres 14
Code coverage* (full report)
* collected from Rust tests only The comment gets automatically updated with the latest test results
7eb96e2 at 2024-09-23T21:26:16.583Z :recycle: |
cc @hlinnaka |
d073e6a
to
742ab85
Compare
We can't FlushOneBuffer when we're in redo-only mode on PageServer, so make execution of that function conditional on us not running in pageserver walredo mode. Fix: Don't flush a buffer in am_wal_redo_postgres mode WalRedoPostgres operates on private buffers, which causes issues with FlushOneBuffer, which expects to handle only shared buffers.
742ab85
to
30674a5
Compare
very strange @hlinnaka @bayandin link:
|
We can't FlushOneBuffer when we're in redo-only mode on PageServer, so make execution of that function conditional on us not running in pageserver walredo mode.
Problem
https://neondb.slack.com/archives/C033RQ5SPDH/p1726847895245409
Summary of changes
We make sure to not call into FlushOneBuffer when we're in WALRedoPostgres mode.
See
Checklist before requesting a review
Checklist before merging