pg-partman
pg-partman
pg_partman creates and maintains time-based and ID-based PostgreSQL partition sets. Its optional background worker can run partition maintenance automatically.
Follow the quick start to set up extension-update email
alerts first, then use the CronJob to install and refresh the catalog. These
examples inherit image references and runtime settings from the catalog. The Cluster YAML
is an excerpt: replace imageCatalogRef: ... with your catalog reference and
keep your existing instance and storage settings.
Usage
1. Add the pg-partman extension image to your Cluster
Add the image to a Cluster and preload the background worker:
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
name: cluster-pg-partman
spec:
imageCatalogRef: ...
postgresql:
shared_preload_libraries:
- pg_partman_bgw
extensions:
- name: pg-partman
2. Enable the extension in a database
Once the extension's files are available in the cluster, you can install it in a database in either of two ways:
- Declaratively, using a CloudNativePG
Databaseresource. - Through SQL, by running
CREATE EXTENSION pg_partman;in the target database.
Platform teams may make extension containers available across their clusters without installing every extension in every database. Install only the extensions a database uses; letting users enable them through SQL alongside the rest of their DDL schema management code can be a convenient approach.
For extensions that normally require superuser privileges, platform teams can use pgextwlist to allow non-superusers to install an administrator-approved selection of extensions.
For pg_partman, create the partman schema first and use
CREATE EXTENSION pg_partman SCHEMA partman;, or set schema: partman in the
declarative extension entry.
3. Verify installation
Connect to the database with psql and run \dx to check the installed extensions.
See the pg_partman documentation for partition-set configuration examples.
Licenses and Copyright
The package copyright and license notice are included in the image under /licenses/postgresql-18-partman/.
Overview
pg_partman creates and maintains time-based and ID-based PostgreSQL partition sets. Its optional background worker can run partition maintenance automatically.
Package details
- Extension version
- 5.5.0
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Trixie · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-partman
- Upstream homepage ↗github.com/pgpartman/pg_partman
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION pg_partman;- SQL version
5.5.0
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'pg_partman_bgw' |
These recipe settings are used in automated smoke tests.
OpenSSF scorecard
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.
View information about checks. Automated results are informational only; some categories may not apply to this project.
Scanned · View OpenSSF report ↗
Dangerous-Workflow10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: no dangerous workflow patterns detected
Binary-Artifacts10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning: no binaries found in the repo
Branch-ProtectionUnknown
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Code-Review4
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 12/28 approved changesets -- score normalized to 4
Maintained10
Determines if the project is "actively maintained".
Reasoning: 3 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0
Determines if the project's workflows follow the principle of least privilege.
Reasoning: detected GitHub workflow tokens with excessive permissions
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Warn: no topLevel permission defined: .github/workflows/release.yml:1
- Info: no jobLevel write permissions found
Fuzzing0
Determines if the project uses fuzzing.
Reasoning: project is not fuzzed
- Warn: no fuzzer integrations found
Pinned-Dependencies0
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: dependency not pinned by hash detected -- score normalized to 0
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/ci.yml/development?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/release.yml/development?enable=pin
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
SAST0
Determines if the project uses static code analysis.
Reasoning: SAST tool is not run on all commits -- score normalized to 0
- Warn: 0 commits out of 17 are checked with a SAST tool
Security-Policy4
Determines if the project has published a security policy.
Reasoning: security policy file detected
- Info: security policy file detected: SECURITY.md:1
- Warn: no linked content found
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
CII-Best-Practices0
Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.
Reasoning: no effort to earn an OpenSSF best practices badge detected
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE.txt:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
pg_partman creates and maintains time-based and ID-based PostgreSQL partition sets. Its optional background worker can run partition maintenance automatically.
Package details
- Extension version
- 5.5.0
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Trixie · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-partman
- Upstream homepage ↗github.com/pgpartman/pg_partman
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION pg_partman;- SQL version
5.5.0
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'pg_partman_bgw' |
These recipe settings are used in automated smoke tests.
OpenSSF scorecard
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.
View information about checks. Automated results are informational only; some categories may not apply to this project.
Scanned · View OpenSSF report ↗
Dangerous-Workflow10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: no dangerous workflow patterns detected
Binary-Artifacts10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning: no binaries found in the repo
Branch-ProtectionUnknown
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Code-Review4
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 12/28 approved changesets -- score normalized to 4
Maintained10
Determines if the project is "actively maintained".
Reasoning: 3 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0
Determines if the project's workflows follow the principle of least privilege.
Reasoning: detected GitHub workflow tokens with excessive permissions
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Warn: no topLevel permission defined: .github/workflows/release.yml:1
- Info: no jobLevel write permissions found
Fuzzing0
Determines if the project uses fuzzing.
Reasoning: project is not fuzzed
- Warn: no fuzzer integrations found
Pinned-Dependencies0
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: dependency not pinned by hash detected -- score normalized to 0
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/ci.yml/development?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/release.yml/development?enable=pin
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
SAST0
Determines if the project uses static code analysis.
Reasoning: SAST tool is not run on all commits -- score normalized to 0
- Warn: 0 commits out of 17 are checked with a SAST tool
Security-Policy4
Determines if the project has published a security policy.
Reasoning: security policy file detected
- Info: security policy file detected: SECURITY.md:1
- Warn: no linked content found
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
CII-Best-Practices0
Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.
Reasoning: no effort to earn an OpenSSF best practices badge detected
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE.txt:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
pg_partman creates and maintains time-based and ID-based PostgreSQL partition sets. Its optional background worker can run partition maintenance automatically.
Package details
- Extension version
- 5.5.0
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Bookworm · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-partman
- Upstream homepage ↗github.com/pgpartman/pg_partman
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION pg_partman;- SQL version
5.5.0
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'pg_partman_bgw' |
These recipe settings are used in automated smoke tests.
OpenSSF scorecard
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.
View information about checks. Automated results are informational only; some categories may not apply to this project.
Scanned · View OpenSSF report ↗
Dangerous-Workflow10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: no dangerous workflow patterns detected
Binary-Artifacts10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning: no binaries found in the repo
Branch-ProtectionUnknown
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Code-Review4
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 12/28 approved changesets -- score normalized to 4
Maintained10
Determines if the project is "actively maintained".
Reasoning: 3 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0
Determines if the project's workflows follow the principle of least privilege.
Reasoning: detected GitHub workflow tokens with excessive permissions
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Warn: no topLevel permission defined: .github/workflows/release.yml:1
- Info: no jobLevel write permissions found
Fuzzing0
Determines if the project uses fuzzing.
Reasoning: project is not fuzzed
- Warn: no fuzzer integrations found
Pinned-Dependencies0
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: dependency not pinned by hash detected -- score normalized to 0
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/ci.yml/development?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/release.yml/development?enable=pin
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
SAST0
Determines if the project uses static code analysis.
Reasoning: SAST tool is not run on all commits -- score normalized to 0
- Warn: 0 commits out of 17 are checked with a SAST tool
Security-Policy4
Determines if the project has published a security policy.
Reasoning: security policy file detected
- Info: security policy file detected: SECURITY.md:1
- Warn: no linked content found
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
CII-Best-Practices0
Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.
Reasoning: no effort to earn an OpenSSF best practices badge detected
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE.txt:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
pg_partman creates and maintains time-based and ID-based PostgreSQL partition sets. Its optional background worker can run partition maintenance automatically.
Package details
- Extension version
- 5.5.0
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Bookworm · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-partman
- Upstream homepage ↗github.com/pgpartman/pg_partman
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION pg_partman;- SQL version
5.5.0
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'pg_partman_bgw' |
These recipe settings are used in automated smoke tests.
OpenSSF scorecard
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.
View information about checks. Automated results are informational only; some categories may not apply to this project.
Scanned · View OpenSSF report ↗
Dangerous-Workflow10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: no dangerous workflow patterns detected
Binary-Artifacts10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning: no binaries found in the repo
Branch-ProtectionUnknown
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Code-Review4
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 12/28 approved changesets -- score normalized to 4
Maintained10
Determines if the project is "actively maintained".
Reasoning: 3 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0
Determines if the project's workflows follow the principle of least privilege.
Reasoning: detected GitHub workflow tokens with excessive permissions
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Warn: no topLevel permission defined: .github/workflows/release.yml:1
- Info: no jobLevel write permissions found
Fuzzing0
Determines if the project uses fuzzing.
Reasoning: project is not fuzzed
- Warn: no fuzzer integrations found
Pinned-Dependencies0
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: dependency not pinned by hash detected -- score normalized to 0
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/ci.yml/development?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/pgpartman/pg_partman/release.yml/development?enable=pin
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
SAST0
Determines if the project uses static code analysis.
Reasoning: SAST tool is not run on all commits -- score normalized to 0
- Warn: 0 commits out of 17 are checked with a SAST tool
Security-Policy4
Determines if the project has published a security policy.
Reasoning: security policy file detected
- Info: security policy file detected: SECURITY.md:1
- Warn: no linked content found
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
CII-Best-Practices0
Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.
Reasoning: no effort to earn an OpenSSF best practices badge detected
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE.txt:0
- Warn: project license file does not contain an FSF or OSI license.
Dependencies
Packages shipped in this image, including the extension itself.
1 packages · Scanned
| Package / installed version | License evidence | Advisories |
|---|---|---|
postgresql-18-partman ↗ 5.5.0-1.pgdg13+2 | PostgreSQL | Yes ↗ |
No packages match these filters. Try a different name or license, or clear the filters.
Dependencies
Packages shipped in this image, including the extension itself.
1 packages · Scanned
| Package / installed version | License evidence | Advisories |
|---|---|---|
postgresql-18-partman ↗ 5.5.0-1.pgdg13+2 | PostgreSQL | Yes ↗ |
No packages match these filters. Try a different name or license, or clear the filters.
Dependencies
Packages shipped in this image, including the extension itself.
1 packages · Scanned
| Package / installed version | License evidence | Advisories |
|---|---|---|
postgresql-18-partman ↗ 5.5.0-1.pgdg12+2 | PostgreSQL | Yes ↗ |
No packages match these filters. Try a different name or license, or clear the filters.
Dependencies
Packages shipped in this image, including the extension itself.
1 packages · Scanned
| Package / installed version | License evidence | Advisories |
|---|---|---|
postgresql-18-partman ↗ 5.5.0-1.pgdg12+2 | PostgreSQL | Yes ↗ |
No packages match these filters. Try a different name or license, or clear the filters.
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-partman/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: pg_partman Source: https://github.com/pgpartman/pg_partman Files: * Copyright: Copyright (c) 2015 OmniTI, Inc. License: PostgreSQL Files: debian/* Copyright: Copyright (c) 2015 Christoph Berg <myon@debian.org> License: PostgreSQL License: PostgreSQL PG Partition Manager (pg_partman) is released under the PostgreSQL License, a liberal Open Source license, similar to the BSD or MIT licenses. . Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. . IN NO EVENT SHALL THE AUTHOR BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. . THE AUTHOR SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE AUTHOR HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: f51964634dabba08832bf51d56d283626fd3022c1824d50e1677f6eaf81bfae8
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-partman/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: pg_partman Source: https://github.com/pgpartman/pg_partman Files: * Copyright: Copyright (c) 2015 OmniTI, Inc. License: PostgreSQL Files: debian/* Copyright: Copyright (c) 2015 Christoph Berg <myon@debian.org> License: PostgreSQL License: PostgreSQL PG Partition Manager (pg_partman) is released under the PostgreSQL License, a liberal Open Source license, similar to the BSD or MIT licenses. . Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. . IN NO EVENT SHALL THE AUTHOR BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. . THE AUTHOR SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE AUTHOR HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: f51964634dabba08832bf51d56d283626fd3022c1824d50e1677f6eaf81bfae8
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-partman/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: pg_partman Source: https://github.com/pgpartman/pg_partman Files: * Copyright: Copyright (c) 2015 OmniTI, Inc. License: PostgreSQL Files: debian/* Copyright: Copyright (c) 2015 Christoph Berg <myon@debian.org> License: PostgreSQL License: PostgreSQL PG Partition Manager (pg_partman) is released under the PostgreSQL License, a liberal Open Source license, similar to the BSD or MIT licenses. . Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. . IN NO EVENT SHALL THE AUTHOR BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. . THE AUTHOR SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE AUTHOR HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: f51964634dabba08832bf51d56d283626fd3022c1824d50e1677f6eaf81bfae8
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-partman/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: pg_partman Source: https://github.com/pgpartman/pg_partman Files: * Copyright: Copyright (c) 2015 OmniTI, Inc. License: PostgreSQL Files: debian/* Copyright: Copyright (c) 2015 Christoph Berg <myon@debian.org> License: PostgreSQL License: PostgreSQL PG Partition Manager (pg_partman) is released under the PostgreSQL License, a liberal Open Source license, similar to the BSD or MIT licenses. . Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. . IN NO EVENT SHALL THE AUTHOR BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. . THE AUTHOR SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE AUTHOR HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: f51964634dabba08832bf51d56d283626fd3022c1824d50e1677f6eaf81bfae8
Versions
Extension versions and the images built from them.
Tagged GHCR builds fetched .
