- 
                Notifications
    You must be signed in to change notification settings 
- Fork 26
Test Postgres 18 #386
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
base: main
Are you sure you want to change the base?
Test Postgres 18 #386
Conversation
| 
 | 
| 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. | 
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.
Just for my understanding. In Postgres 18, would the current replication slot automatically continue working after recreating the publication?
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.