Repository navigation
source-postgres: improve UI message and doc on xmin - #38848
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Octavia Squidington III (octavia-squidington-iii)
added
area/connectors
Evan Tahler (evantahler)
approved these changes
Jun 2, 2024
Contributor
|
Feel free to update the docs in the same PR! For the docs, you can run the site locally as you develop - https://github.com/airbytehq/airbyte/blob/master/docusaurus/README.md |
Octavia Squidington III (octavia-squidington-iii)
added
the
area/documentation
Yue Li (theyueli)
changed the title
Contributor
Author
sounds good, done. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #38850
The current recommendation for using xmin on the UI of the Postgres source connector is misleading; we want to say that the database is not experiencing a high transaction rate such that it is less likely to trigger xmin wraparound soon.
Added sections on the doc and troubleshooting page regarding Xmin as well.