Skip to content
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

Add comment explaining why it is safe to use FirstNormalTransactionXid for oldestActiveXid while replica startup #388

Merged
merged 1 commit into from
Feb 22, 2024

Conversation

knizhnik
Copy link

No description provided.

…d for oldestActiveXid while replica startup
@knizhnik knizhnik merged commit 79b6351 into REL_15_STABLE_neon Feb 22, 2024
@knizhnik knizhnik deleted the oldest_active_xid_v15 branch February 22, 2024 19:53
skyzh added a commit that referenced this pull request Mar 22, 2024
…actionXid for oldestActiveXid while replica startup (#388)"

This reverts commit 79b6351.
skyzh added a commit that referenced this pull request Mar 22, 2024
* Revert "Add comment explaining why it is safe to use FirstNormalTransactionXid for oldestActiveXid while replica startup (#388)"

This reverts commit 79b6351.

* Revert "Set wasShutdown=true during hot-standby replica startup only when primary is not alive (#364)"

This reverts commit be91d91.
tristan957 pushed a commit that referenced this pull request May 10, 2024
…recovery.

Rust's postgres_backend currently is too dummy to handle it properly: reading
happens in separate thread which just ignores CopyDone. Instead, writer thread
must get aware of termination and send CommandComplete. Also reading socket must
be transferred back to postgres_backend (or connection terminated completely
after COPY). Let's do that after more basic safkeeper refactoring and right now
cover this up to make tests pass.

ref #388
tristan957 pushed a commit that referenced this pull request May 10, 2024
…d for oldestActiveXid while replica startup (#388)

Co-authored-by: Konstantin Knizhnik <knizhnik@neon.tech>
tristan957 pushed a commit that referenced this pull request May 10, 2024
* Revert "Add comment explaining why it is safe to use FirstNormalTransactionXid for oldestActiveXid while replica startup (#388)"

This reverts commit 79b6351.

* Revert "Set wasShutdown=true during hot-standby replica startup only when primary is not alive (#364)"

This reverts commit be91d91.
tristan957 pushed a commit that referenced this pull request May 20, 2024
…d for oldestActiveXid while replica startup (#388)

Co-authored-by: Konstantin Knizhnik <knizhnik@neon.tech>
tristan957 pushed a commit that referenced this pull request May 20, 2024
* Revert "Add comment explaining why it is safe to use FirstNormalTransactionXid for oldestActiveXid while replica startup (#388)"

This reverts commit 79b6351.

* Revert "Set wasShutdown=true during hot-standby replica startup only when primary is not alive (#364)"

This reverts commit be91d91.
poojanilangekar pushed a commit to umd-dslam/sunstorm-postgres that referenced this pull request Aug 26, 2024
…recovery.

Rust's postgres_backend currently is too dummy to handle it properly: reading
happens in separate thread which just ignores CopyDone. Instead, writer thread
must get aware of termination and send CommandComplete. Also reading socket must
be transferred back to postgres_backend (or connection terminated completely
after COPY). Let's do that after more basic safkeeper refactoring and right now
cover this up to make tests pass.

ref neondatabase#388
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