periods
periods
PERIODs and SYSTEM VERSIONING for PostgreSQL. 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 periods extension image to your Cluster
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
name: cluster-periods
spec:
imageCatalogRef: ...
postgresql:
extensions:
- name: periods
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 periods;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.
Install btree_gist, then periods in that order.
3. Verify installation
Connect to the database with psql and run \dx to check the installed extensions.
Operation and privileges
Temporal history uses ordinary PostgreSQL tables on the CNPG data volume. To retire history, suspend system versioning with periods.drop_system_versioning, delete expired history rows using SQL, then re-enable versioning. Define your retention interval and execute maintenance through an external SQL scheduler.
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
PostgreSQL. Redistribution notices are preserved under /licenses/.
Overview
PERIODs and SYSTEM VERSIONING for PostgreSQL. Upstream documentation .
Package details
- Extension version
- 1.2.3
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Trixie · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/postgresql-periods
- Upstream homepage ↗github.com/xocolatl/periods
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
btree_gist(from the PostgreSQL base image)- SQL installation
CREATE EXTENSION periods;- SQL version
1.2— differs from extension version 1.2.3
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 · 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-Protection0
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection not enabled on development/release branches
- Warn: branch protection not enabled for branch 'master'
Code-Review0
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 0/30 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/regression.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/regression.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/xocolatl/periods/regression.yml/master?enable=pin
- Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned
SAST0
Determines if the project uses static code analysis.
Reasoning: no SAST tool detected
- Warn: no pull requests merged into dev branch
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-TestsUnknown
Determines if the project runs tests before pull requests are merged.
Reasoning: no pull request found
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 5 contributing companies or organizations
- Info: found contributions from: Debian, cybertec-postgresql, debian, 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: PostgreSQL License: LICENSE:0
Overview
PERIODs and SYSTEM VERSIONING for PostgreSQL. Upstream documentation .
Package details
- Extension version
- 1.2.3
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Trixie · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/postgresql-periods
- Upstream homepage ↗github.com/xocolatl/periods
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
btree_gist(from the PostgreSQL base image)- SQL installation
CREATE EXTENSION periods;- SQL version
1.2— differs from extension version 1.2.3
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 · 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-Protection0
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection not enabled on development/release branches
- Warn: branch protection not enabled for branch 'master'
Code-Review0
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 0/30 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/regression.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/regression.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/xocolatl/periods/regression.yml/master?enable=pin
- Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned
SAST0
Determines if the project uses static code analysis.
Reasoning: no SAST tool detected
- Warn: no pull requests merged into dev branch
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-TestsUnknown
Determines if the project runs tests before pull requests are merged.
Reasoning: no pull request found
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 5 contributing companies or organizations
- Info: found contributions from: Debian, cybertec-postgresql, debian, 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: PostgreSQL License: LICENSE:0
Overview
PERIODs and SYSTEM VERSIONING for PostgreSQL. Upstream documentation .
Package details
- Extension version
- 1.2.3
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Bookworm · amd64
Project links
- Debian source package ↗tracker.debian.org/pkg/postgresql-periods
- Upstream homepage ↗github.com/xocolatl/periods
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
btree_gist(from the PostgreSQL base image)- SQL installation
CREATE EXTENSION periods;- SQL version
1.2— differs from extension version 1.2.3
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 · 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-Protection0
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection not enabled on development/release branches
- Warn: branch protection not enabled for branch 'master'
Code-Review0
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 0/30 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/regression.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/regression.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/xocolatl/periods/regression.yml/master?enable=pin
- Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned
SAST0
Determines if the project uses static code analysis.
Reasoning: no SAST tool detected
- Warn: no pull requests merged into dev branch
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-TestsUnknown
Determines if the project runs tests before pull requests are merged.
Reasoning: no pull request found
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 5 contributing companies or organizations
- Info: found contributions from: Debian, cybertec-postgresql, debian, 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: PostgreSQL License: LICENSE:0
Overview
PERIODs and SYSTEM VERSIONING for PostgreSQL. Upstream documentation .
Package details
- Extension version
- 1.2.3
- Image built
- Publisher
- cnpg-extensions
- Build
- Debian
- Platform
- PG 18 · Bookworm · arm64
Project links
- Debian source package ↗tracker.debian.org/pkg/postgresql-periods
- Upstream homepage ↗github.com/xocolatl/periods
Links from package metadata, recipe update rules, or reviewed upstream mappings.
Database setup
- Required extensions
btree_gist(from the PostgreSQL base image)- SQL installation
CREATE EXTENSION periods;- SQL version
1.2— differs from extension version 1.2.3
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 · 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-Protection0
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning: branch protection not enabled on development/release branches
- Warn: branch protection not enabled for branch 'master'
Code-Review0
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning: Found 0/30 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/regression.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/regression.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/xocolatl/periods/regression.yml/master?enable=pin
- Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned
SAST0
Determines if the project uses static code analysis.
Reasoning: no SAST tool detected
- Warn: no pull requests merged into dev branch
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-TestsUnknown
Determines if the project runs tests before pull requests are merged.
Reasoning: no pull request found
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 5 contributing companies or organizations
- Info: found contributions from: Debian, cybertec-postgresql, debian, 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: PostgreSQL License: LICENSE:0
Dependencies
Packages shipped in this image, including the extension itself.
1 packages · Scanned
| Package / installed version | License evidence | Advisories |
|---|---|---|
postgresql-18-periods ↗ 1.2.3-2.pgdg13+1 | PostgreSQL | 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-periods ↗ 1.2.3-2.pgdg13+1 | PostgreSQL | 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-periods ↗ 1.2.3-2.pgdg12+1 | PostgreSQL | 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-periods ↗ 1.2.3-2.pgdg12+1 | PostgreSQL | 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-periods/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: periods
Source: https://github.com/xocolatl/periods
Files: *
Copyright: Portions Copyright (c) 1996-2019, PostgreSQL Global Development Group
Portions Copyright (c) 1994, The Regents of the University of California
License: PostgreSQL
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 UNIVERSITY OF CALIFORNIA 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 UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
.
THE UNIVERSITY OF CALIFORNIA 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 UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: 9f2e0eafd610d2d4aa53f5a6225597cf19acc74d0533b72b0440cb5508a440d2
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-periods/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: periods
Source: https://github.com/xocolatl/periods
Files: *
Copyright: Portions Copyright (c) 1996-2019, PostgreSQL Global Development Group
Portions Copyright (c) 1994, The Regents of the University of California
License: PostgreSQL
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 UNIVERSITY OF CALIFORNIA 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 UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
.
THE UNIVERSITY OF CALIFORNIA 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 UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: 9f2e0eafd610d2d4aa53f5a6225597cf19acc74d0533b72b0440cb5508a440d2
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-periods/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: periods
Source: https://github.com/xocolatl/periods
Files: *
Copyright: Portions Copyright (c) 1996-2019, PostgreSQL Global Development Group
Portions Copyright (c) 1994, The Regents of the University of California
License: PostgreSQL
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 UNIVERSITY OF CALIFORNIA 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 UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
.
THE UNIVERSITY OF CALIFORNIA 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 UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: 9f2e0eafd610d2d4aa53f5a6225597cf19acc74d0533b72b0440cb5508a440d2
Licenses
Original license files shipped in the selected container image.
1 file read directly from /licenses.
/licenses/postgresql-18-periods/copyrightRead notice
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: periods
Source: https://github.com/xocolatl/periods
Files: *
Copyright: Portions Copyright (c) 1996-2019, PostgreSQL Global Development Group
Portions Copyright (c) 1994, The Regents of the University of California
License: PostgreSQL
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 UNIVERSITY OF CALIFORNIA 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 UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
.
THE UNIVERSITY OF CALIFORNIA 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 UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
SHA256: 9f2e0eafd610d2d4aa53f5a6225597cf19acc74d0533b72b0440cb5508a440d2
Versions
Extension versions and the images built from them.
Tagged GHCR builds fetched .
