Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions website/docs/release_notes/v1.27.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,15 +24,15 @@ on the release branch in GitHub.
requiring explicit storage account keys or SAS tokens.
([#9468](https://github.com/cloudnative-pg/cloudnative-pg/pull/9468)) <!-- 1.27 1.25 -->

- Added support for PostgreSQL extension names containing underscores (e.g.,
`pg_ivm`, `pg_stat_statements`). Extension names with underscores are
### Fixes

- Fixed validation of PostgreSQL extension names containing underscores (e.g.,
`pg_partman`, `pg_ivm`). Extension names with underscores are
automatically sanitized to use hyphens for Kubernetes volume names while
preserving the original name in mount paths. Webhook validation prevents
naming conflicts after sanitization. Contributed by @shusaan.
([#9386](https://github.com/cloudnative-pg/cloudnative-pg/pull/9386)) <!-- 1.27 -->

### Fixes

- Fixed a critical issue where the `TimelineID` in the cluster status was not
reset to 1 after a major version upgrade. Because `pg_upgrade` initializes a
new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt
Expand Down
8 changes: 4 additions & 4 deletions website/docs/release_notes/v1.28.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,15 +44,15 @@ on the release branch in GitHub.
requiring explicit storage account keys or SAS tokens.
([#9468](https://github.com/cloudnative-pg/cloudnative-pg/pull/9468)) <!-- 1.27 1.25 -->

- Added support for PostgreSQL extension names containing underscores (e.g.,
`pg_ivm`, `pg_stat_statements`). Extension names with underscores are
### Fixes

- Fixed validation of PostgreSQL extension names containing underscores (e.g.,
`pg_partman`, `pg_ivm`). Extension names with underscores are
automatically sanitized to use hyphens for Kubernetes volume names while
preserving the original name in mount paths. Webhook validation prevents
naming conflicts after sanitization. Contributed by @shusaan.
([#9386](https://github.com/cloudnative-pg/cloudnative-pg/pull/9386)) <!-- 1.27 -->

### Fixes

- Fixed a critical issue where the `TimelineID` in the cluster status was not
reset to 1 after a major version upgrade. Because `pg_upgrade` initializes a
new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt
Expand Down
8 changes: 4 additions & 4 deletions website/versioned_docs/version-1.27/release_notes/v1.27.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,15 +24,15 @@ on the release branch in GitHub.
requiring explicit storage account keys or SAS tokens.
([#9468](https://github.com/cloudnative-pg/cloudnative-pg/pull/9468)) <!-- 1.27 1.25 -->

- Added support for PostgreSQL extension names containing underscores (e.g.,
`pg_ivm`, `pg_stat_statements`). Extension names with underscores are
### Fixes

- Fixed validation of PostgreSQL extension names containing underscores (e.g.,
`pg_partman`, `pg_ivm`). Extension names with underscores are
automatically sanitized to use hyphens for Kubernetes volume names while
preserving the original name in mount paths. Webhook validation prevents
naming conflicts after sanitization. Contributed by @shusaan.
([#9386](https://github.com/cloudnative-pg/cloudnative-pg/pull/9386)) <!-- 1.27 -->

### Fixes

- Fixed a critical issue where the `TimelineID` in the cluster status was not
reset to 1 after a major version upgrade. Because `pg_upgrade` initializes a
new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt
Expand Down
8 changes: 4 additions & 4 deletions website/versioned_docs/version-1.28/release_notes/v1.27.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,15 +24,15 @@ on the release branch in GitHub.
requiring explicit storage account keys or SAS tokens.
([#9468](https://github.com/cloudnative-pg/cloudnative-pg/pull/9468)) <!-- 1.27 1.25 -->

- Added support for PostgreSQL extension names containing underscores (e.g.,
`pg_ivm`, `pg_stat_statements`). Extension names with underscores are
### Fixes

- Fixed validation of PostgreSQL extension names containing underscores (e.g.,
`pg_partman`, `pg_ivm`). Extension names with underscores are
automatically sanitized to use hyphens for Kubernetes volume names while
preserving the original name in mount paths. Webhook validation prevents
naming conflicts after sanitization. Contributed by @shusaan.
([#9386](https://github.com/cloudnative-pg/cloudnative-pg/pull/9386)) <!-- 1.27 -->

### Fixes

- Fixed a critical issue where the `TimelineID` in the cluster status was not
reset to 1 after a major version upgrade. Because `pg_upgrade` initializes a
new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt
Expand Down
8 changes: 4 additions & 4 deletions website/versioned_docs/version-1.28/release_notes/v1.28.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,15 +44,15 @@ on the release branch in GitHub.
requiring explicit storage account keys or SAS tokens.
([#9468](https://github.com/cloudnative-pg/cloudnative-pg/pull/9468)) <!-- 1.27 1.25 -->

- Added support for PostgreSQL extension names containing underscores (e.g.,
`pg_ivm`, `pg_stat_statements`). Extension names with underscores are
### Fixes

- Fixed validation of PostgreSQL extension names containing underscores (e.g.,
`pg_partman`, `pg_ivm`). Extension names with underscores are
automatically sanitized to use hyphens for Kubernetes volume names while
preserving the original name in mount paths. Webhook validation prevents
naming conflicts after sanitization. Contributed by @shusaan.
([#9386](https://github.com/cloudnative-pg/cloudnative-pg/pull/9386)) <!-- 1.27 -->

### Fixes

- Fixed a critical issue where the `TimelineID` in the cluster status was not
reset to 1 after a major version upgrade. Because `pg_upgrade` initializes a
new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt
Expand Down