-
Notifications
You must be signed in to change notification settings - Fork 115
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
Bail if upstream URL is malformed #82
Comments
Postgres can be configured to allow passwordless login as well. It does, however, always require a username, as far as I've read. |
In MySQL, you can create a superuser with no username or password:
When such a user exists, ReadySet will connect and replicate from a URL of the form:
So we don't want to require username + password for MySQL deployments. |
Postgres username missing:
Postgres password missing:
Postgres bad username/password:
Conclusions: It might be possible to differentiate between recoverable and unrecoverable errors based on this information, but it would involve matching on strings and/or opaque error codes, which is brittle. We should just check for these fields manually. |
Blocked because I think the most robust way to handle these errors is to treat them as unrecoverable where they are now, rather than add logic elsewhere to try and catch them early. |
Omitting the username or password also leads to a replicator failure loop. |
Some discussion on whether readyset might ever want to deal with postgres upstream URLs that don't contain a database name: https://readyset-workspace.slack.com/archives/C01HF1WTP6Y/p1686944393015599 |
In at least one case (postgres missing db name), a malformed upstream URL results in errors that could be cleaner (indefinitely repeating replicator errors).
We should make this case a permanent failure with a user-friendly message, and investigate/fix possible others.
From SyncLinear.com | REA-2917
The text was updated successfully, but these errors were encountered: