Skip to content

Conversation

@rkistner
Copy link
Contributor

@rkistner rkistner commented Oct 29, 2025

Postgres 18 was released on September 25. It should work without any changes in powersync-service - this merely confirms it by adding it to our test matrix.

I modified one test slightly, since Postgres 18 now has more robust handling for dropped + re-created publications.

@changeset-bot
Copy link

changeset-bot bot commented Oct 29, 2025

⚠️ No Changeset found

Latest commit: 316db4a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@rkistner rkistner marked this pull request as ready for review October 30, 2025 01:28
await context.replicateSnapshot();
}).rejects.toThrowError(MissingReplicationSlotError);
// No error expected in Postres 18
// TODO: introduce new test scenario for Postgres 18 that _does_ invalidate the replication slot.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Just for my understanding. In Postgres 18, would the current replication slot automatically continue working after recreating the publication?

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.

3 participants