plproxy
plproxy
database partitioning system for PostgreSQL 18. Upstream documentation.
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.
Supported images
PostgreSQL 18; Debian Trixie and Bookworm; amd64 and arm64 build targets.
Usage
1. Add the plproxy extension image to your Cluster
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
name: cluster-plproxy
spec:
imageCatalogRef: ...
postgresql:
extensions:
- name: plproxy
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 plproxy;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.
Operation and privileges
PL/Proxy forwards SQL through PostgreSQL connections. Its dynamically linked libpq and transitive libraries are supplied by the matching CNPG minimal base (which includes psql); no runtime installation is needed. Configure connection strings and credentials through SQL and Kubernetes Secrets, and allow only required outbound destinations.
Dependencies and updates
The image contains only the PGDG package server payload and license notices. The matching CNPG minimal image supplies PostgreSQL, libc and its base runtime. Project automation tracks package updates and rebuilds the extension images. Use the catalog maintenance schedule in the quick start to consume published PostgreSQL and extension image updates. Monitor pending SQL extension upgrades and review them separately; SQL versions need not match package versions.
Licenses and ownership
ISC. Redistribution notices are preserved under /licenses/.
PL/Proxy CONNECT strings use libpq keyword/value syntax (for example, host=cluster-rw dbname=app user=proxy_user), not connection URIs: the plugin adds connection options to the string. Supply credentials through your deployment Secrets.
Overview
database partitioning system for PostgreSQL 18. Upstream documentation .
Package details
- Extension version
- 2.12.0
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Trixie · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/postgresql-plproxy
- Upstream homepage ↗plproxy.github.io/
- Source repository ↗github.com/plproxy/plproxy
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION plproxy;- SQL version
2.12.0
PostgreSQL parameters
None specified
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-Protection3
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'
- Warn: could not determine whether codeowners review is allowed
- Warn: no status checks found to merge onto branch 'master'
- Warn: PRs are not required to make changes on branch 'master'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings
Code-Review0
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 1/26 approved changesets -- score normalized to 0
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/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:40: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:120: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:175: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:53: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
- Info: 0 out of 5 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 6 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
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: COPYRIGHT:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
database partitioning system for PostgreSQL 18. Upstream documentation .
Package details
- Extension version
- 2.12.0
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Trixie · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/postgresql-plproxy
- Upstream homepage ↗plproxy.github.io/
- Source repository ↗github.com/plproxy/plproxy
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION plproxy;- SQL version
2.12.0
PostgreSQL parameters
None specified
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-Protection3
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'
- Warn: could not determine whether codeowners review is allowed
- Warn: no status checks found to merge onto branch 'master'
- Warn: PRs are not required to make changes on branch 'master'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings
Code-Review0
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 1/26 approved changesets -- score normalized to 0
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/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:40: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:120: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:175: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:53: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
- Info: 0 out of 5 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 6 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
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: COPYRIGHT:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
database partitioning system for PostgreSQL 18. Upstream documentation .
Package details
- Extension version
- 2.12.0
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Bookworm · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/postgresql-plproxy
- Upstream homepage ↗plproxy.github.io/
- Source repository ↗github.com/plproxy/plproxy
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION plproxy;- SQL version
2.12.0
PostgreSQL parameters
None specified
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-Protection3
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'
- Warn: could not determine whether codeowners review is allowed
- Warn: no status checks found to merge onto branch 'master'
- Warn: PRs are not required to make changes on branch 'master'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings
Code-Review0
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 1/26 approved changesets -- score normalized to 0
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/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:40: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:120: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:175: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:53: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
- Info: 0 out of 5 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 6 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
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: COPYRIGHT:0
- Warn: project license file does not contain an FSF or OSI license.
Overview
database partitioning system for PostgreSQL 18. Upstream documentation .
Package details
- Extension version
- 2.12.0
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Bookworm · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/postgresql-plproxy
- Upstream homepage ↗plproxy.github.io/
- Source repository ↗github.com/plproxy/plproxy
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
- None specified
- SQL installation
CREATE EXTENSION plproxy;- SQL version
2.12.0
PostgreSQL parameters
None specified
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-Protection3
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'
- Warn: could not determine whether codeowners review is allowed
- Warn: no status checks found to merge onto branch 'master'
- Warn: PRs are not required to make changes on branch 'master'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings
Code-Review0
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 1/26 approved changesets -- score normalized to 0
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/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:40: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:120: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:175: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:53: update your workflow using https://app.stepsecurity.io/secureworkflow/plproxy/plproxy/release.yml/master?enable=pin
- Info: 0 out of 5 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 6 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
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: COPYRIGHT: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-plproxy ↗ 2.12.0-1.pgdg13+3 | ISC | 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-plproxy ↗ 2.12.0-1.pgdg13+3 | ISC | 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-plproxy ↗ 2.12.0-1.pgdg12+3 | ISC | 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-plproxy ↗ 2.12.0-1.pgdg12+3 | ISC | 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-plproxy/copyrightRead notice
This package was debianized by Fernando Ike de Oliveira
<fike@midstorm.org> on Tue, 05 Jun 2007 23:19:56 -0300.
Upstream Authors: Sven Suursoho <sven.suursoho@skype.net>,
Marko Kreen <marko.kreen@skype.net>
Copyright (c) 2006 Sven Suursoho, Skype Technologies OÜ
Copyright (c) 2007-2009 Marko Kreen, Skype Technologies OÜ
Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
SHA256: 791489a9a0a7165e3343ff597dc67f0e380f9009a904d1124db9e910ba18cdaa
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-plproxy/copyrightRead notice
This package was debianized by Fernando Ike de Oliveira
<fike@midstorm.org> on Tue, 05 Jun 2007 23:19:56 -0300.
Upstream Authors: Sven Suursoho <sven.suursoho@skype.net>,
Marko Kreen <marko.kreen@skype.net>
Copyright (c) 2006 Sven Suursoho, Skype Technologies OÜ
Copyright (c) 2007-2009 Marko Kreen, Skype Technologies OÜ
Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
SHA256: 791489a9a0a7165e3343ff597dc67f0e380f9009a904d1124db9e910ba18cdaa
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-plproxy/copyrightRead notice
This package was debianized by Fernando Ike de Oliveira
<fike@midstorm.org> on Tue, 05 Jun 2007 23:19:56 -0300.
Upstream Authors: Sven Suursoho <sven.suursoho@skype.net>,
Marko Kreen <marko.kreen@skype.net>
Copyright (c) 2006 Sven Suursoho, Skype Technologies OÜ
Copyright (c) 2007-2009 Marko Kreen, Skype Technologies OÜ
Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
SHA256: 791489a9a0a7165e3343ff597dc67f0e380f9009a904d1124db9e910ba18cdaa
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-plproxy/copyrightRead notice
This package was debianized by Fernando Ike de Oliveira
<fike@midstorm.org> on Tue, 05 Jun 2007 23:19:56 -0300.
Upstream Authors: Sven Suursoho <sven.suursoho@skype.net>,
Marko Kreen <marko.kreen@skype.net>
Copyright (c) 2006 Sven Suursoho, Skype Technologies OÜ
Copyright (c) 2007-2009 Marko Kreen, Skype Technologies OÜ
Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
SHA256: 791489a9a0a7165e3343ff597dc67f0e380f9009a904d1124db9e910ba18cdaa
Versions
Extension versions and the images built from them.
Tagged GHCR builds fetched .
