Skip to content

fix: drop schema specifier when enabling pgmq - #4391

Merged
sweatybridge merged 1 commit into
developfrom
fix-pgmq
Nov 4, 2025
Merged

sweatybridge merged 1 commit into
developfrom
fix-pgmq

Conversation

@sweatybridge

@sweatybridge sweatybridge commented Oct 31, 2025 •

Copy link
Copy Markdown
Contributor

What kind of change does this PR introduce?

Bug fix

What is the new behavior?

When running db dump, the pgmq schema is excluded because it's managed by extension.

Dropping the specifier allows pgmq extension to be created without running into missing schema error.

Additional context

Add any other context or screenshots.

@sweatybridge
sweatybridge requested a review from a team as a code owner October 31, 2025 08:27
@coveralls

Copy link
Copy Markdown

Pull Request Test Coverage Report for Build 18967002153

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 5 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.03%) to 54.673%

Files with Coverage Reduction New Missed Lines %
internal/gen/keys/keys.go 5 12.9%
Totals Coverage Status
Change from base Build 18965934599: -0.03%
Covered Lines: 6388
Relevant Lines: 11684

💛 - Coveralls

@jgoux jgoux left a comment

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.

What bug triggered this change?

@sweatybridge

Copy link
Copy Markdown
Contributor Author

added PR description, basically the same fix as pgsodium.

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.

3 participants