show-plans
show-plans
pg_show_plans shows the query plans of currently running PostgreSQL statements. Plans can be returned as plain text, JSON, YAML, or XML.
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 show-plans extension image to your Cluster
Add the image to a Cluster and preload pg_show_plans:
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
name: cluster-show-plans
spec:
imageCatalogRef: ...
postgresql:
shared_preload_libraries:
- pg_show_plans
extensions:
- name: show-plans
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_show_plans;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.
3. Verify installation
Connect to the database with psql and run \dx to check the installed extensions.
Inspect plans for currently running statements:
CREATE EXTENSION IF NOT EXISTS pg_show_plans;
SELECT * FROM pg_show_plans;
SELECT * FROM pg_show_plans_q;
Licenses and Copyright
The package copyright and license notice are included in the image under /licenses/postgresql-18-show-plans/.
Overview
pg_show_plans shows the query plans of currently running PostgreSQL statements. Plans can be returned as plain text, JSON, YAML, or XML.
Package details
- Extension version
- 2.1.8
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Trixie · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-show-plans
- Upstream homepage ↗github.com/cybertec-postgresql/pg_show_plans
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION pg_show_plans;- SQL version
2.1— differs from extension version 2.1.8
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'pg_show_plans' |
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 · Download cached scan ↓
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-Protection5
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection is not maximal on development and all release branches
- Info: 'allow deletion' disabled on branch 'master'
- Info: 'force pushes' disabled on branch 'master'
- Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
- Info: 'stale review dismissal' is required to merge on branch 'master'
- Warn: required approving review count is 1 on branch 'master'
- Warn: codeowners review is not required on branch 'master'
- Warn: 'last push approval' is disabled on branch 'master'
- Warn: no status checks found to merge onto branch 'master'
- Info: PRs are required in order to make changes on branch 'master'
Code-Review0
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 0/27 approved changesets -- score normalized to 0
Dependency-Update-Tool0
Determines if the project uses a dependency update tool.
Reasoning: no update tool detected
- Warn: no dependency update tool configurations found
Maintained0
Determines if the project is "actively maintained".
Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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/installcheck.yml:1
- Info: no jobLevel write permissions found
Vulnerabilities10
Determines if the project has open, known unfixed vulnerabilities.
Reasoning: 0 existing vulnerabilities detected
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/installcheck.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/cybertec-postgresql/pg_show_plans/installcheck.yml/master?enable=pin
- Info: 0 out of 1 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 14 are checked with a SAST tool
Security-Policy0
Determines if the project has published a security policy.
Reasoning: security policy file not detected
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
CI-Tests0
Determines if the project runs tests before pull requests are merged.
Reasoning: 0 out of 11 merged PRs checked by a CI test -- score normalized to 0
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
Contributors10
Determines if the project has a set of contributors from multiple organizations (e.g., companies).
Reasoning: project has 6 contributing companies or organizations
- Info: found contributions from: Debian, cybertec-postgresql, debian, interdb, oftc, powa-team
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
pg_show_plans shows the query plans of currently running PostgreSQL statements. Plans can be returned as plain text, JSON, YAML, or XML.
Package details
- Extension version
- 2.1.8
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Trixie · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-show-plans
- Upstream homepage ↗github.com/cybertec-postgresql/pg_show_plans
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION pg_show_plans;- SQL version
2.1— differs from extension version 2.1.8
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'pg_show_plans' |
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 · Download cached scan ↓
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-Protection5
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection is not maximal on development and all release branches
- Info: 'allow deletion' disabled on branch 'master'
- Info: 'force pushes' disabled on branch 'master'
- Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
- Info: 'stale review dismissal' is required to merge on branch 'master'
- Warn: required approving review count is 1 on branch 'master'
- Warn: codeowners review is not required on branch 'master'
- Warn: 'last push approval' is disabled on branch 'master'
- Warn: no status checks found to merge onto branch 'master'
- Info: PRs are required in order to make changes on branch 'master'
Code-Review0
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 0/27 approved changesets -- score normalized to 0
Dependency-Update-Tool0
Determines if the project uses a dependency update tool.
Reasoning: no update tool detected
- Warn: no dependency update tool configurations found
Maintained0
Determines if the project is "actively maintained".
Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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/installcheck.yml:1
- Info: no jobLevel write permissions found
Vulnerabilities10
Determines if the project has open, known unfixed vulnerabilities.
Reasoning: 0 existing vulnerabilities detected
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/installcheck.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/cybertec-postgresql/pg_show_plans/installcheck.yml/master?enable=pin
- Info: 0 out of 1 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 14 are checked with a SAST tool
Security-Policy0
Determines if the project has published a security policy.
Reasoning: security policy file not detected
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
CI-Tests0
Determines if the project runs tests before pull requests are merged.
Reasoning: 0 out of 11 merged PRs checked by a CI test -- score normalized to 0
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
Contributors10
Determines if the project has a set of contributors from multiple organizations (e.g., companies).
Reasoning: project has 6 contributing companies or organizations
- Info: found contributions from: Debian, cybertec-postgresql, debian, interdb, oftc, powa-team
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
pg_show_plans shows the query plans of currently running PostgreSQL statements. Plans can be returned as plain text, JSON, YAML, or XML.
Package details
- Extension version
- 2.1.8
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Bookworm · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-show-plans
- Upstream homepage ↗github.com/cybertec-postgresql/pg_show_plans
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION pg_show_plans;- SQL version
2.1— differs from extension version 2.1.8
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'pg_show_plans' |
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 · Download cached scan ↓
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-Protection5
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection is not maximal on development and all release branches
- Info: 'allow deletion' disabled on branch 'master'
- Info: 'force pushes' disabled on branch 'master'
- Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
- Info: 'stale review dismissal' is required to merge on branch 'master'
- Warn: required approving review count is 1 on branch 'master'
- Warn: codeowners review is not required on branch 'master'
- Warn: 'last push approval' is disabled on branch 'master'
- Warn: no status checks found to merge onto branch 'master'
- Info: PRs are required in order to make changes on branch 'master'
Code-Review0
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 0/27 approved changesets -- score normalized to 0
Dependency-Update-Tool0
Determines if the project uses a dependency update tool.
Reasoning: no update tool detected
- Warn: no dependency update tool configurations found
Maintained0
Determines if the project is "actively maintained".
Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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/installcheck.yml:1
- Info: no jobLevel write permissions found
Vulnerabilities10
Determines if the project has open, known unfixed vulnerabilities.
Reasoning: 0 existing vulnerabilities detected
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/installcheck.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/cybertec-postgresql/pg_show_plans/installcheck.yml/master?enable=pin
- Info: 0 out of 1 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 14 are checked with a SAST tool
Security-Policy0
Determines if the project has published a security policy.
Reasoning: security policy file not detected
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
CI-Tests0
Determines if the project runs tests before pull requests are merged.
Reasoning: 0 out of 11 merged PRs checked by a CI test -- score normalized to 0
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
Contributors10
Determines if the project has a set of contributors from multiple organizations (e.g., companies).
Reasoning: project has 6 contributing companies or organizations
- Info: found contributions from: Debian, cybertec-postgresql, debian, interdb, oftc, powa-team
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
pg_show_plans shows the query plans of currently running PostgreSQL statements. Plans can be returned as plain text, JSON, YAML, or XML.
Package details
- Extension version
- 2.1.8
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Bookworm · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-show-plans
- Upstream homepage ↗github.com/cybertec-postgresql/pg_show_plans
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION pg_show_plans;- SQL version
2.1— differs from extension version 2.1.8
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'pg_show_plans' |
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 · Download cached scan ↓
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-Protection5
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection is not maximal on development and all release branches
- Info: 'allow deletion' disabled on branch 'master'
- Info: 'force pushes' disabled on branch 'master'
- Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
- Info: 'stale review dismissal' is required to merge on branch 'master'
- Warn: required approving review count is 1 on branch 'master'
- Warn: codeowners review is not required on branch 'master'
- Warn: 'last push approval' is disabled on branch 'master'
- Warn: no status checks found to merge onto branch 'master'
- Info: PRs are required in order to make changes on branch 'master'
Code-Review0
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 0/27 approved changesets -- score normalized to 0
Dependency-Update-Tool0
Determines if the project uses a dependency update tool.
Reasoning: no update tool detected
- Warn: no dependency update tool configurations found
Maintained0
Determines if the project is "actively maintained".
Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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/installcheck.yml:1
- Info: no jobLevel write permissions found
Vulnerabilities10
Determines if the project has open, known unfixed vulnerabilities.
Reasoning: 0 existing vulnerabilities detected
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/installcheck.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/cybertec-postgresql/pg_show_plans/installcheck.yml/master?enable=pin
- Info: 0 out of 1 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 14 are checked with a SAST tool
Security-Policy0
Determines if the project has published a security policy.
Reasoning: security policy file not detected
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
CI-Tests0
Determines if the project runs tests before pull requests are merged.
Reasoning: 0 out of 11 merged PRs checked by a CI test -- score normalized to 0
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
Contributors10
Determines if the project has a set of contributors from multiple organizations (e.g., companies).
Reasoning: project has 6 contributing companies or organizations
- Info: found contributions from: Debian, cybertec-postgresql, debian, interdb, oftc, powa-team
License9
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE: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-show-plans ↗ 2.1.8-1.pgdg13+2 | LicenseRef-PostgreSQL-Cybertec | No ↗ |
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-show-plans ↗ 2.1.8-1.pgdg13+2 | LicenseRef-PostgreSQL-Cybertec | No ↗ |
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-show-plans ↗ 2.1.8-1.pgdg12+2 | LicenseRef-PostgreSQL-Cybertec | No ↗ |
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-show-plans ↗ 2.1.8-1.pgdg12+2 | LicenseRef-PostgreSQL-Cybertec | No ↗ |
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-show-plans/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: pg_show_plans
Source: https://github.com/cybertec-postgresql/pg_show_plans
Files: *
Copyright: Portions Copyright (c) 1996-2023, PostgreSQL Global Development Group
Portions Copyright (c) 1994, The Regents of the University of California
Copyright (c) 2019-2023, CYBERTEC PostgreSQL International GmbH
License: PostgreSQL-Cybertec
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 CYBERTEC PostgreSQL International GmbH 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 CYBERTEC PostgreSQL International GmbH HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
.
CYBERTEC PostgreSQL International GmbH 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 CYBERTEC PostgreSQL International GmbH HAS NO OBLIGATIONS TO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: 3cc5fb0fd20f9c17a9888d9edaa08435945cabefe05c170f313edbc21d4cfc24
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-show-plans/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: pg_show_plans
Source: https://github.com/cybertec-postgresql/pg_show_plans
Files: *
Copyright: Portions Copyright (c) 1996-2023, PostgreSQL Global Development Group
Portions Copyright (c) 1994, The Regents of the University of California
Copyright (c) 2019-2023, CYBERTEC PostgreSQL International GmbH
License: PostgreSQL-Cybertec
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 CYBERTEC PostgreSQL International GmbH 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 CYBERTEC PostgreSQL International GmbH HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
.
CYBERTEC PostgreSQL International GmbH 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 CYBERTEC PostgreSQL International GmbH HAS NO OBLIGATIONS TO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: 3cc5fb0fd20f9c17a9888d9edaa08435945cabefe05c170f313edbc21d4cfc24
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-show-plans/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: pg_show_plans
Source: https://github.com/cybertec-postgresql/pg_show_plans
Files: *
Copyright: Portions Copyright (c) 1996-2023, PostgreSQL Global Development Group
Portions Copyright (c) 1994, The Regents of the University of California
Copyright (c) 2019-2023, CYBERTEC PostgreSQL International GmbH
License: PostgreSQL-Cybertec
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 CYBERTEC PostgreSQL International GmbH 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 CYBERTEC PostgreSQL International GmbH HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
.
CYBERTEC PostgreSQL International GmbH 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 CYBERTEC PostgreSQL International GmbH HAS NO OBLIGATIONS TO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: 3cc5fb0fd20f9c17a9888d9edaa08435945cabefe05c170f313edbc21d4cfc24
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-show-plans/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: pg_show_plans
Source: https://github.com/cybertec-postgresql/pg_show_plans
Files: *
Copyright: Portions Copyright (c) 1996-2023, PostgreSQL Global Development Group
Portions Copyright (c) 1994, The Regents of the University of California
Copyright (c) 2019-2023, CYBERTEC PostgreSQL International GmbH
License: PostgreSQL-Cybertec
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 CYBERTEC PostgreSQL International GmbH 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 CYBERTEC PostgreSQL International GmbH HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
.
CYBERTEC PostgreSQL International GmbH 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 CYBERTEC PostgreSQL International GmbH HAS NO OBLIGATIONS TO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: 3cc5fb0fd20f9c17a9888d9edaa08435945cabefe05c170f313edbc21d4cfc24
Versions
Extension versions and the images built from them.
Tagged GHCR builds fetched .
