Repository navigation
Store U+0000 in strings on PostgreSQL and MongoDB #368
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
Open
+3,019
−145
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
17e7f2f
fix(storage): store U+0000 in strings on PostgreSQL and MongoDB
LeeroyHannigan 482b0d8
fix(storage-postgres): derive restored key columns and index rows fro…
LeeroyHannigan e3eeb0b
fix(migrate): name the catalog store sessions so the exclusive-access…
LeeroyHannigan e5384cc
refactor(app): move the migrate application_name helper into its own …
LeeroyHannigan 8817b23
fix(app): replace an application_name already in the migrate connecti…
LeeroyHannigan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,86 @@ | ||
| // SPDX-License-Identifier: Apache-2.0 | ||
|
|
||
| //! The `application_name` the migrate command sets on the PostgreSQL sessions | ||
| //! it opens through the configured connection string. | ||
|
|
||
| /// `application_name` the migrate command carries on every PostgreSQL session | ||
| /// it opens. The exclusive-access check for `004_escape_control_chars` | ||
| /// (`extenddb-storage-postgres`, `migrations::MIGRATE_APPLICATION_NAME`) counts | ||
| /// every session on the catalog and data databases except those with this | ||
| /// name. The bootstrapper sets it on its own pools; the catalog stores opened | ||
| /// by `CatalogResourceTagStep` connect through the configured connection | ||
| /// string and would otherwise be counted as foreign sessions, which makes | ||
| /// `migrate --yes` refuse every upgrade from a release without that migration. | ||
| const MIGRATE_APPLICATION_NAME: &str = "extenddb-migrate"; | ||
|
|
||
| /// `connection` with its `application_name` set to `extenddb-migrate` when it is | ||
| /// a PostgreSQL URL. An `application_name` already in the query string is | ||
| /// replaced: the exclusive-access check skips only sessions with this exact | ||
| /// name, so a URL that keeps an operator's name would make `migrate --yes` | ||
| /// count its own sessions as foreign and refuse. Other backends' connection | ||
| /// strings are returned unchanged. | ||
| pub(crate) fn with_migrate_application_name(connection: &str) -> String { | ||
| let is_postgres = | ||
| connection.starts_with("postgres://") || connection.starts_with("postgresql://"); | ||
| if !is_postgres { | ||
| return connection.to_owned(); | ||
| } | ||
| let (base, query) = connection.split_once('?').unwrap_or((connection, "")); | ||
| let mut params: Vec<&str> = query | ||
| .split('&') | ||
| .filter(|p| !p.is_empty() && !p.starts_with("application_name=")) | ||
| .collect(); | ||
| let ours = format!("application_name={MIGRATE_APPLICATION_NAME}"); | ||
| params.push(&ours); | ||
| format!("{base}?{}", params.join("&")) | ||
| } | ||
|
|
||
| #[cfg(test)] | ||
| mod application_name_tests { | ||
| use super::with_migrate_application_name; | ||
|
|
||
| #[test] | ||
| fn a_postgres_url_without_a_query_string_gets_the_name() { | ||
| assert_eq!( | ||
| with_migrate_application_name("postgresql://app:pw@db:5432/extenddb_catalog"), | ||
| "postgresql://app:pw@db:5432/extenddb_catalog?application_name=extenddb-migrate" | ||
| ); | ||
| assert_eq!( | ||
| with_migrate_application_name("postgres://db/cat"), | ||
| "postgres://db/cat?application_name=extenddb-migrate" | ||
| ); | ||
| } | ||
|
|
||
| #[test] | ||
| fn a_postgres_url_with_a_query_string_gets_the_name_appended() { | ||
| assert_eq!( | ||
| with_migrate_application_name("postgresql://db/cat?sslmode=require"), | ||
| "postgresql://db/cat?sslmode=require&application_name=extenddb-migrate" | ||
| ); | ||
| } | ||
|
|
||
| #[test] | ||
| fn an_existing_application_name_is_replaced() { | ||
| assert_eq!( | ||
| with_migrate_application_name("postgresql://db/cat?application_name=ops"), | ||
| "postgresql://db/cat?application_name=extenddb-migrate" | ||
| ); | ||
| assert_eq!( | ||
| with_migrate_application_name( | ||
| "postgresql://db/cat?sslmode=require&application_name=ops&connect_timeout=5" | ||
| ), | ||
| "postgresql://db/cat?sslmode=require&connect_timeout=5&application_name=extenddb-migrate" | ||
| ); | ||
| } | ||
|
|
||
| #[test] | ||
| fn other_backends_are_unchanged() { | ||
| for given in [ | ||
| "/var/lib/extenddb/extenddb.sqlite", | ||
| "mongodb://127.0.0.1:27017/?replicaSet=rs0", | ||
| "cassandra://127.0.0.1:9042", | ||
| ] { | ||
| assert_eq!(with_migrate_application_name(given), given); | ||
| } | ||
| } | ||
| } |
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Non-blocking: this decoder changes how a legacy field name containing U+0001 U+0001 or U+0001 U+0002 reads back — silently, with no migration and no startup gate, disclosed only in the upgrade manual. The exposure is genuinely narrow (attribute names containing U+0001), so skipping the migration is defensible, but Postgres got a startup refusal for the same class of hazard and MongoDB got a paragraph. Is a one-time startup marker (refuse until the operator acknowledges, like the Postgres gate but with nothing to rewrite) cheap enough to close the asymmetry? If not, a sentence here pointing at the manual section would at least make the tradeoff visible at the code site.
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.
I went with the code-site statement rather than a startup marker. The exposure needs a legacy attribute name containing U+0001 immediately followed by U+0001 or U+0002, and a marker here would have nothing to rewrite, so it would add an acknowledgement step to every MongoDB upgrade for that case.
item_data_to_jsonnow carries the tradeoff and points at the upgrade manual's Data Migrations section; the PR body says the same under Not in this change. If you would rather have the gate anyway, say so and I will add it as a settings document thatextenddb initandextenddb migrate --yeswrite.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.
Unchanged since the 13 Oct reply:
item_data_to_json(crates/storage-mongodb/src/data/mod.rs) still states the tradeoff and points at the upgrade manual's Data Migrations section, and there is no startup marker. The offer to add one as a settings document written byextenddb initandextenddb migrate --yesstands if you want it.