Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Add a Postgres REPLICA IDENTITY to tables that do not have an implicit one. This should allow use of Postgres logical replication.#16456

Merged
reivilibre merged 12 commits into
developfrom
rei/replica_identities
Nov 13, 2023
Merged

Add a Postgres REPLICA IDENTITY to tables that do not have an implicit one. This should allow use of Postgres logical replication.#16456
reivilibre merged 12 commits into
developfrom
rei/replica_identities

Conversation

@reivilibre
Copy link
Copy Markdown
Contributor

Fixes: #16224

Base: develop

Original commit schedule, with full messages:

  1. Add Postgres replica identities to tables that don't have an implicit one
    Fixes All tables in Postgres should have a REPLICA IDENTITY available so that Postgres logical replication can be used #16224

@reivilibre reivilibre force-pushed the rei/replica_identities branch 6 times, most recently from ad592a0 to 417f5c0 Compare October 9, 2023 15:22
Signed-off-by: Olivier Wilkinson (reivilibre) <oliverw@matrix.org>
@reivilibre reivilibre force-pushed the rei/replica_identities branch from 417f5c0 to 6fcc720 Compare October 9, 2023 16:32
@reivilibre reivilibre marked this pull request as ready for review October 9, 2023 16:40
@reivilibre reivilibre requested a review from a team as a code owner October 9, 2023 16:40
Comment thread changelog.d/16456.misc
@reivilibre reivilibre force-pushed the rei/replica_identities branch from a1afdc2 to 89ebcd6 Compare November 10, 2023 14:53
@reivilibre reivilibre requested a review from clokep November 10, 2023 15:12
Comment thread tests/storage/test_database.py Outdated
@clokep
Copy link
Copy Markdown
Member

clokep commented Nov 13, 2023

Although looks like your new test is failing?

@reivilibre
Copy link
Copy Markdown
Contributor Author

Although looks like your new test is failing?

oid is a 'hidden attribute' in Postgres 11 (but not 12+) which means you have to be very explicit about selecting it, it turns out.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Ah I think these will all go away in #16522, but no reason not to have it be correct for now.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

ohhhh that's why these were there a while ago, went away and now came back

@reivilibre reivilibre merged commit 69afe3f into develop Nov 13, 2023
@reivilibre reivilibre deleted the rei/replica_identities branch November 13, 2023 16:03
erikjohnston added a commit that referenced this pull request Nov 16, 2023
…an implicit one. This should allow use of Postgres logical replication. (#16456)"

This reverts commit 69afe3f.
@erikjohnston erikjohnston mentioned this pull request Nov 16, 2023
erikjohnston added a commit that referenced this pull request Nov 16, 2023
…an implicit one. This should allow use of Postgres logical replication. (#16456)"

This reverts commit 69afe3f.
erikjohnston added a commit that referenced this pull request Nov 16, 2023
…an implicit one. This should allow use of Postgres logical replication. (#16456)" (#16651)

This reverts commit 69afe3f.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

All tables in Postgres should have a REPLICA IDENTITY available so that Postgres logical replication can be used

2 participants