pg-crash
pg_crash
pg_crash is a PostgreSQL extension designed for fault injection and chaos engineering. It allows administrators to simulate various failure scenarios—such as backend crashes and signal handling issues—to verify the resilience of High Availability (HA) clusters and self-healing mechanisms.
Caution
DO NOT USE THIS IMAGE IN PRODUCTION. This extension is designed to intentionally destabilize and terminate PostgreSQL processes. Deploying it in production will cause service downtime and potential data availability issues.
Only deploy this extension in dedicated test or staging namespaces. Consider using Kubernetes admission controllers or OPA/Gatekeeper policies to prevent accidental deployment to production clusters.
This extension image is maintained by the CNPG project and supersedes the
pgcrash-containers project.
Usage
The pg_crash extension must be loaded via shared_preload_libraries. It
operates by periodically sending random signals (selected from a user-defined
list) to PostgreSQL backend processes.
The following example configures a cluster to experience "Chaos" by randomly sending signals every 60 seconds. This is ideal for testing how quickly CloudNativePG detects a failure and promotes a new primary.
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
name: cluster-pg-crash
spec:
imageName: ghcr.io/cloudnative-pg/postgresql:18-minimal-trixie
instances: 3
storage:
size: 1Gi
postgresql:
extensions:
- name: pg-crash
image:
# renovate: suite=trixie-pgdg depName=postgresql-18-pg-crash
reference: ghcr.io/cloudnative-pg/pg-crash:0.3-18-trixie
shared_preload_libraries:
- pg_crash
parameters:
log_min_messages: ‘DEBUG1’
# See https://www.postgresql.org/docs/current/server-shutdown.html
# SIGHUP (1) - Reload
# SIGINT (2) - Fast shutdown
# SIGQUIT (3) - Immediate shutdown
# SIGTERM (15) - Smart shutdown
crash.signals: ‘1 2 3 15’
crash.delay: ‘60’
Licenses and Copyright
pg_crash:
- Copyright: (c) 2017, 2025 CYBERTEC PostgreSQL International GmbH
- License: BSD 3-Clause License
All relevant license and copyright information for the pg-crash extension
and its dependencies are bundled within the image at:
/licenses/
By using this image, you agree to comply with the terms of the licenses contained therein.
Overview
pg_crash is a PostgreSQL extension designed for fault injection and chaos engineering . It allows administrators to simulate various failure scenarios—such as backend crashes and signal handling issues—to verify the resilience of High Availability (HA) clusters and self-healing mechanisms.
Package details
- Extension version
- 0.3
- Image built
- Publisher
- cloudnative-pg
- Build
- Debian
- Platform
- PG 18 · Trixie · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-crash
- Upstream homepage ↗github.com/cybertec-postgresql/pg_crash
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
- This recipe does not use
CREATE EXTENSION. - SQL version
- Not recorded
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'pg_crash' |
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-WorkflowUnknown
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: no workflows found
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 1/21 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-PermissionsUnknown
Determines if the project's workflows follow the principle of least privilege.
Reasoning: No tokens 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-DependenciesUnknown
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: no dependencies found
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 2 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 1 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, freelance postgresql engineer / consultant, oftc, powa-team
License10
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: BSD 3-Clause "New" or "Revised" License: LICENSE:0
Overview
pg_crash is a PostgreSQL extension designed for fault injection and chaos engineering . It allows administrators to simulate various failure scenarios—such as backend crashes and signal handling issues—to verify the resilience of High Availability (HA) clusters and self-healing mechanisms.
Package details
- Extension version
- 0.3
- Image built
- Publisher
- cloudnative-pg
- Build
- Debian
- Platform
- PG 18 · Trixie · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-crash
- Upstream homepage ↗github.com/cybertec-postgresql/pg_crash
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
- This recipe does not use
CREATE EXTENSION. - SQL version
- Not recorded
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'pg_crash' |
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-WorkflowUnknown
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: no workflows found
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 1/21 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-PermissionsUnknown
Determines if the project's workflows follow the principle of least privilege.
Reasoning: No tokens 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-DependenciesUnknown
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: no dependencies found
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 2 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 1 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, freelance postgresql engineer / consultant, oftc, powa-team
License10
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: BSD 3-Clause "New" or "Revised" License: LICENSE:0
Overview
pg_crash is a PostgreSQL extension designed for fault injection and chaos engineering . It allows administrators to simulate various failure scenarios—such as backend crashes and signal handling issues—to verify the resilience of High Availability (HA) clusters and self-healing mechanisms.
Package details
- Extension version
- 0.3
- Image built
- Publisher
- cloudnative-pg
- Build
- Debian
- Platform
- PG 18 · Bookworm · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-crash
- Upstream homepage ↗github.com/cybertec-postgresql/pg_crash
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
- This recipe does not use
CREATE EXTENSION. - SQL version
- Not recorded
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'pg_crash' |
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-WorkflowUnknown
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: no workflows found
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 1/21 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-PermissionsUnknown
Determines if the project's workflows follow the principle of least privilege.
Reasoning: No tokens 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-DependenciesUnknown
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: no dependencies found
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 2 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 1 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, freelance postgresql engineer / consultant, oftc, powa-team
License10
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: BSD 3-Clause "New" or "Revised" License: LICENSE:0
Overview
pg_crash is a PostgreSQL extension designed for fault injection and chaos engineering . It allows administrators to simulate various failure scenarios—such as backend crashes and signal handling issues—to verify the resilience of High Availability (HA) clusters and self-healing mechanisms.
Package details
- Extension version
- 0.3
- Image built
- Publisher
- cloudnative-pg
- Build
- Debian
- Platform
- PG 18 · Bookworm · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/pg-crash
- Upstream homepage ↗github.com/cybertec-postgresql/pg_crash
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
- This recipe does not use
CREATE EXTENSION. - SQL version
- Not recorded
PostgreSQL parameters
| Parameter | Value |
|---|---|
shared_preload_libraries | 'pg_crash' |
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-WorkflowUnknown
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning: no workflows found
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 1/21 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-PermissionsUnknown
Determines if the project's workflows follow the principle of least privilege.
Reasoning: No tokens 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-DependenciesUnknown
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning: no dependencies found
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 2 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 1 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, freelance postgresql engineer / consultant, oftc, powa-team
License10
Determines if the project has defined a license.
Reasoning: license file detected
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: BSD 3-Clause "New" or "Revised" License: LICENSE:0
Dependencies
Packages shipped in this image, including the extension itself.
This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.
Dependencies
Packages shipped in this image, including the extension itself.
This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.
Dependencies
Packages shipped in this image, including the extension itself.
This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.
Dependencies
Packages shipped in this image, including the extension itself.
This image is published by CloudNativePG. A reliable SBOM inventory of its shipped dependencies is not available yet.
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-pg-crash/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: pg-crash Source: https://github.com/cybertec-postgresql/pg_crash Files: * Copyright: Copyright (c) 2017, 2025 CYBERTEC PostgreSQL International GmbH License: BSD All rights reserved. . Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: . * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. . * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. . * Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. . THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
SHA256: b9a69ee4249d0e149accf5a7bf1445951859bf68d402730621bc6cb37121069e
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-pg-crash/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: pg-crash Source: https://github.com/cybertec-postgresql/pg_crash Files: * Copyright: Copyright (c) 2017, 2025 CYBERTEC PostgreSQL International GmbH License: BSD All rights reserved. . Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: . * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. . * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. . * Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. . THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
SHA256: b9a69ee4249d0e149accf5a7bf1445951859bf68d402730621bc6cb37121069e
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-pg-crash/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: pg-crash Source: https://github.com/cybertec-postgresql/pg_crash Files: * Copyright: Copyright (c) 2017, 2025 CYBERTEC PostgreSQL International GmbH License: BSD All rights reserved. . Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: . * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. . * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. . * Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. . THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
SHA256: b9a69ee4249d0e149accf5a7bf1445951859bf68d402730621bc6cb37121069e
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-pg-crash/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: pg-crash Source: https://github.com/cybertec-postgresql/pg_crash Files: * Copyright: Copyright (c) 2017, 2025 CYBERTEC PostgreSQL International GmbH License: BSD All rights reserved. . Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: . * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. . * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. . * Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. . THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
SHA256: b9a69ee4249d0e149accf5a7bf1445951859bf68d402730621bc6cb37121069e
Versions
Extension versions and the images built from them.
Tagged GHCR builds fetched .
