Skip to content

[Source-postgres] : Throw exception if there are any streams acively undergoing vacuum - #41651

Merged
Akash Kulkarni (akashkulk) merged 3 commits into
masterfrom
akash/pg-remove-vacuum
Jul 12, 2024
Merged

Akash Kulkarni (akashkulk) merged 3 commits into
masterfrom
akash/pg-remove-vacuum

Conversation

@akashkulk

Copy link
Copy Markdown
Contributor

This case never occurs as it involves holding an exclusive lock on the table. If it doess happen, the query will not succeed. We can simplify code by throwing an exception if this ever occurs.

@vercel

vercel Bot commented Jul 12, 2024 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
airbyte-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 12, 2024 8:02pm

if (!streamsUnderVacuum.isEmpty()) {
throw new ConfigErrorException(
"Postgres database is undergoing a full vacuum - cannot proceed with the sync. Please sync again when the vacuum is finished.");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do we really want this to be a ConfigErrorException? Don't we want to retry syncing later on?

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.

Good point, will change to TransientErrorException

This branch was successfully deployed

1 active deployment
Preview — d6e0a2c2 Deployed Jul 12, 2024 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/connectors Connector related issues area/documentation Improvements or additions to documentation connectors/source/postgres

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants