Summary
The user is experiencing errors with a Postgres connector related to maximum slot reservations exceeding. They are considering changing the LSN commit behavior configuration to resolve the issue.
Question
I’m working with a postgres connector via supabase to bigquery and have someone experiencing errors regarding maximum slot reservations exceeding:
Detail: This slot has been invalidated because it exceeded the maximum reserved size.```
The configuration for the LSN commit behavior is currently set to "While Reading Data". Could switching to "After Loading Data in the Destination" resolve the issue? It's not my airbyte instance so I don't have control of changing it. I do want to make sure I can advise the best course of action.
<br>
---
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1724857985534939) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
["postgres-connector", "supabase", "bigquery", "logical-replication-slot", "LSN-commit-behavior"]
</sub>