Skip to content

ncm-postgresql: Make pg_version mandatory in schema#1857

Merged
jrha merged 1 commit intoquattor:mainfrom
jrha:postgresql-version-mandatory
Feb 20, 2026
Merged

ncm-postgresql: Make pg_version mandatory in schema#1857
jrha merged 1 commit intoquattor:mainfrom
jrha:postgresql-version-mandatory

Conversation

@jrha
Copy link
Member

@jrha jrha commented Feb 20, 2026

This is technically backwards incompatible, but you can't manage a DB without it.

Resolves #1569.

This is technically backwards incompatible, but you can't manage a DB without it.
@jrha jrha added this to the 26.2 milestone Feb 20, 2026
Copy link
Contributor

@ned21 ned21 left a comment

Choose a reason for hiding this comment

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

Is the panlint failure expected when modifying a schema here?

This is ultimately passed to CAF::Process which I seem to recall ensures things like shell escapes are not processed.

@jrha
Copy link
Member Author

jrha commented Feb 20, 2026

The panlint failure is a missing parameter to panlint, fixed in quattor/release#378.

@jrha jrha merged commit a9ab0ad into quattor:main Feb 20, 2026
2 of 3 checks passed
@jrha jrha deleted the postgresql-version-mandatory branch February 20, 2026 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

ncm-postgresql: Does not work with newer postgres versions

2 participants