Skip to content

Correctly handle COMBCID flag in WAL #457

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

Merged
merged 3 commits into from
Aug 13, 2024

Conversation

knizhnik
Copy link

@knizhnik knizhnik commented Aug 2, 2024

  1. Fix bug storing in WAL command identifier of old tuple
  2. Store HEAP_COMBOCID flag in WAL
@knizhnik knizhnik force-pushed the preserve_combocid_v15 branch from 4e65327 to dffcdaa Compare August 13, 2024 16:13
@knizhnik knizhnik merged commit 46b4b23 into REL_15_STABLE_neon Aug 13, 2024
@knizhnik knizhnik deleted the preserve_combocid_v15 branch August 13, 2024 19:06
knizhnik added a commit to neondatabase/neon that referenced this pull request Aug 14, 2024
## Problem

See #8499

## Summary of changes

Save HEAP_COMBOCID flag in WAL and do not clear it in redo handlers.

Related Postgres PRs:
neondatabase/postgres#457
neondatabase/postgres#458
neondatabase/postgres#459


## Checklist before requesting a review

- [ ] I have performed a self-review of my code.
- [ ] If it is a core feature, I have added thorough tests.
- [ ] Do we need to implement analytics? if so did you add the relevant
metrics to the dashboard?
- [ ] If this PR requires public announcement, mark it with
/release-notes label and add several sentences in this section.

## Checklist before merging

- [ ] Do not forget to reformat commit message to not include the above
checklist

---------

Co-authored-by: Konstantin Knizhnik <[email protected]>
Co-authored-by: Heikki Linnakangas <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants