Skip to content
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

Replace period on replication slot name #92

Merged
merged 1 commit into from
Dec 2, 2024

Conversation

eminano
Copy link
Collaborator

@eminano eminano commented Dec 2, 2024

Resolves #90

@eminano eminano requested a review from exekias December 2, 2024 10:23
Copy link

github-actions bot commented Dec 2, 2024

Merging this branch will not change overall coverage

Impacted Packages Coverage Δ 🤖
pgstream/internal/postgres 0.00% (ø)

Coverage by file

Changed files (no unit tests)

Changed File Coverage Δ Total Covered Missed 🤖
pgstream/internal/postgres/pg_replication_conn.go 0.00% (ø) 0 0 0

Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code.

Changed unit test files

  • pgstream/internal/postgres/pg_test.go

@eminano eminano merged commit bd02bf7 into main Dec 2, 2024
6 checks passed
@eminano eminano deleted the replace-period-replication-slot-name branch December 2, 2024 10:27
@@ -121,6 +122,9 @@ func (c *ReplicationConn) Close(ctx context.Context) error {
}

func DefaultReplicationSlotName(dbName string) string {
// sanitise the dbName before creating the replication slot name to ensure
// the name does not contain invalid characters.
dbName = strings.ReplaceAll(dbName, ".", "_")
Copy link
Member

Choose a reason for hiding this comment

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

I wonder if there are other chars that would need replacing 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error when using a db that has dot (.) in the name
2 participants