You are here

PostreSQL.org

Subscribe to PostreSQL.org feed
PostgreSQL news
Updated: 2 days 2 hours ago

pgagroal 0.7.0

2020, May 26 - 02:00

The pgagroal community is happy to announce version 0.7.0.

New features

  • Prometheus support
  • Remote management
  • Ability to disconnect idle clients after the specified number of seconds

Plus various improvements and bug fixes.

pgagroal

pgagroal is a high-performance protocol-native connection pool for PostgreSQL.

Features

  • High performance
  • Connection pool
  • Limit connections for users and databases
  • Prefill support
  • Remove idle connections
  • Perform connection validation
  • Enable / disable database access
  • Graceful / fast shutdown
  • Prometheus support
  • Remote management
  • Transport Layer Security (TLS) v1.2+ support
  • Daemon mode
  • User vault

Learn more on our web site or GitHub. Follow on Twitter.

pgagroal is released under the 3-clause BSD license, and is sponsored by Red Hat.

Categories: Informatika

Pgpool-II 4.1.2, 4.0.9, 3.7.14, 3.6.21 and 3.5.25 are now officially released.

2020, May 25 - 02:00
What is Pgpool-II?

Pgpool-II is a tool to add useful features to PostgreSQL, including:

  • connection pooling
  • load balancing
  • automatic fail over and more.
Minor releases

Pgpool Global Development Group is pleased to announce the availability of following versions of Pgpool-II:

  • 4.1.2
  • 4.0.9
  • 3.7.14
  • 3.6.21
  • 3.5.25

Release notes for versions prior 3.6 are no longer included in the source code.

Please take a look at release notes.

You can download the source code and RPMs.

Categories: Informatika

PostgreSQL 13 Beta 1 Released!

2020, May 21 - 02:00

The PostgreSQL Global Development Group announces that the first beta release of PostgreSQL 13 is now available for download. This release contains previews of all features that will be available in the final release of PostgreSQL 13, though some details of the release could change before then.

You can find information about all of the features and changes found in PostgreSQL 13 in the release notes:

https://www.postgresql.org/docs/13/release-13.html

In the spirit of the open source PostgreSQL community, we strongly encourage you to test the new features of PostgreSQL 13 in your systems to help us eliminate any bugs or other issues that may exist. While we do not advise you to run PostgreSQL 13 Beta 1 in your production environments, we encourage you to find ways to run your typical application workloads against this beta release.

Your testing and feedback will help the community ensure that the PostgreSQL 13 release upholds our standards of providing a stable, reliable release of the world's most advanced open source relational database. You can read more about our beta testing process and how you can contribute here:

https://www.postgresql.org/developer/beta/

PostgreSQL 13 Feature Highlights Functionality

There are many new features in PostgreSQL 13 that help improve the overall performance of PostgreSQL while making it even easier to develop applications.

B-tree indexes, the standard index of PostgreSQL, received improvements for how they handle duplicate data. These enhancements help to shrink index size and improve lookup speed, particularly for indexes that contain repeated values.

PostgreSQL 13 adds incremental sorting, which accelerates sorting data when data that is sorted from earlier parts of a query are already sorted. Additionally, queries with OR clauses or IN/ANY constant lists can use extended statistics (created via CREATE STATISTICS), which can lead to better planning and performance gains. PostgreSQL 13 can now use disk storage for hash aggregation (used as part of aggregate queries) with large aggregation sets.

There are more improvements added to PostgreSQL's partitioning functionality in this release, including an increased number of cases where a join directly between partitioned tables can occur, which can improve overall query execution time. Partitioned tables now support BEFORE row-level triggers, and a partitioned table can now be fully replicated via logical replication without having to publish individual partitions.

PostgreSQL 13 brings more convenience to writing queries with features like FETCH FIRST WITH TIES, which returns any additional rows that match the last row. There is also the addition of the .datetime() function for jsonpath queries, which will automatically convert a date-like or time-like string to the appropriate PostgreSQL date/time datatype. It is also even easier now to generate random UUIDs, as the gen_random_uuid() function can be used without having to enable any extensions.

Administration

One of the most anticipated features of PostgreSQL 13 is the ability for the VACUUM command to process indexes in parallel. This functionality can be accessed using the new PARALLEL option on the VACUUM command (or --parallel on vacuumdb), which allows you to specify the number of parallel workers to use for vacuuming indexes. Note that this does not work with the FULL option.

The reindexdb command has also added parallelism with the new --jobs flag, which lets you specify the number of concurrent sessions to use when reindexing a database.

PostgreSQL 13 introduces the concept of a "trusted extension", which allows for a superuser to specify extensions that a user can install in their database so long as they have a CREATE privilege.

This release includes more ways to monitor activity within a PostgreSQL database: PostgreSQL 13 can now track WAL usage statistics and the progress of streaming base backups, and the progress of an ANALYZE command. pg_basebackup can also generate a manifest that can be used to verify the integrity of a backup using a new tool called pg_verifybackup. It is also now possible to limit the amount of WAL space reserved by replication slots.

A new flag for pg_dump, --include-foreign-data, includes data from servers referenced by foreign data wrappers in the dump output.

The pg_rewind command also has improvements in PostgreSQL 13. In addition to pg_rewind automatically performing crash recovery, you can now use it to configure standby PostgreSQL instances using the --write-recovery-conf flag. pg_rewind can also use the restore_command of the target instance to fetch needed write-ahead logs.

Security

PostgreSQL continues to improve on its security capabilities in this latest release, introducing several features to help further deploy PostgreSQL safely.

libpq, the connection library that powers psql and many PostgreSQL connection drivers, includes several new parameters to help secure connections. PostgreSQL 13 introduces the channel_binding connection parameters, which lets a client specify that they want to require the channel binding functionality as part of SCRAM. Additionally, a client that is using a password protected TLS certificate can now specify its password using the sslpassword parameter. PostgreSQL 13 also adds support for DER encoded certificates.

The PostgreSQL foreign data wrapper (postgres_fdw) also received several enhancements to how it can secure connections, including the ability to use certificate-based authentication to connect to other PostgreSQL clusters. Additionally, unprivileged accounts can now connect to another PostgreSQL database via the postgres_fdw without using a password.

Other Highlights

PostgreSQL 13 continues to improve operability on Windows, as now users who run PostgreSQL on Windows now have the option to connect over UNIX domain sockets.

The PostgreSQL 13 documentation adds a glossary of terms to help people familiarize themselves with both PostgreSQL and general database concepts. This coincides with a significant rework in the display of functions and operators in tables, which helps to improve readability both on the web and in the PDF documentation.

The pgbench utility, used for performance testing, now supports the ability to partition its "accounts" table, making it easier to benchmark workloads that contain partitions.

psql now includes the \warn command that is similar to the \echo command in terms of outputting data, except \warn sends it to stderr. And in case you need additional guidance on any of the PostgreSQL commands, the --help flag now includes a link to https://www.postgresql.org.

Additional Features

Many other new features and improvements have been added to PostgreSQL 13, some of which may be as or more important to your use case than what is mentioned above. Please see the release notes for a complete list of new and changed features:

https://www.postgresql.org/docs/13/release-13.html

Testing for Bugs & Compatibility

The stability of each PostgreSQL release greatly depends on you, the community, to test the upcoming version with your workloads and testing tools in order to find bugs and regressions before the general availability of PostgreSQL 13. As this is a Beta, minor changes to database behaviors, feature details, and APIs are still possible. Your feedback and testing will help determine the final tweaks on the new features, so please test in the near future. The quality of user testing helps determine when we can make a final release.

A list of open issues is publicly available in the PostgreSQL wiki. You can report bugs using this form on the PostgreSQL website:

https://www.postgresql.org/account/submitbug/

Beta Schedule

This is the first beta release of version 13. The PostgreSQL Project will release additional betas as required for testing, followed by one or more release candidates, until the final release in late 2020. For further information please see the Beta Testing page.

Links
Categories: Informatika

PostgreSQL 12.3, 11.8, 10.13, 9.6.18, and 9.5.22 Released!

2020, May 14 - 02:00

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 12.3, 11.8, 10.13, 9.6.18, and 9.5.22. This release fixes one security issue found in the PostgreSQL server and over 75 bugs reported over the last three months.

Please plan to update at your earliest convenience.

Security Issues
  • CVE-2020-10733: Windows installer runs executables from uncontrolled directories.

Versions Affected: 9.5 - 12. The security team does not test unsupported versions, but this issue existed before PostgreSQL 9.5.

The Windows installer for PostgreSQL invokes system-provided executables that do not have fully-qualified paths. Executables in the directory where the installer loads or the current working directory take precedence over the intended executables. An attacker having permission to add files into one of those directories can use this to execute arbitrary code with the installer's administrative rights.

The PostgreSQL project thanks Hou JingYi (@hjy79425575) for reporting this problem.

Bug Fixes and Improvements

This update also fixes over 75 bugs that were reported in the last several months. Some of these issues affect only version 12, but may also affect all supported versions.

Some of these fixes include:

  • Several fixes for GENERATED columns, including an issue where it was possible to crash or corrupt data in a table when the output of the generated column was the exact copy of a physical column on the table, e.g. if the expression called a function which could return its own input.
  • Several fixes for ALTER TABLE, including ensuring the SET STORAGE directive is propagated to a table's indexes.
  • Fix a potential race condition when using DROP OWNED BY while another session is deleting the same objects.
  • Allow for a partition to be detached when it has inherited ROW triggers.
  • Several fixes for REINDEX CONCURRENTLY, particularly with issues when a REINDEX CONCURRENTLY operation fails.
  • Fix crash when COLLATE is applied to an uncollatable type in a partition bound expression.
  • Fix performance regression in floating point overflow/underflow detection.
  • Several fixes for full text search, particularly with phrase searching.
  • Fix query-lifespan memory leak for a set-returning function used in a query's FROM clause.
  • Several reporting fixes for the output of VACUUM VERBOSE.
  • Allow input of type circle to accept the format (x,y),r, which is specified in the documentation.
  • Allow for the get_bit() and set_bit() functions to not fail on bytea strings longer than 256MB.
  • Avoid premature recycling of WAL segments during crash recovery, which could lead to WAL segments being recycled before being archived.
  • Avoid attempting to fetch nonexistent WAL files from archive storage during recovery by skipping irrelevant timelines.
  • Several fixes for logical replication and replication slots.
  • Fix several race conditions in synchronous standby management, including one that occurred when changing the synchronous_standby_names setting.
  • Several fixes for GSSAPI support, include a fix for a memory leak that occurred when using GSSAPI encryption.
  • Ensure that members of the pg_read_all_stats role can read all statistics views.
  • Fix performance regression in information_schema.triggers view.
  • Fix memory leak in libpq when using sslmode=verify-full.
  • Fix crash in psql when attempting to re-establish a failed connection.
  • Allow tab-completion of the filename argument to \gx command in psql.
  • Add pg_dump support for ALTER ... DEPENDS ON EXTENSION.
  • Several other fixes for pg_dump, which include dumping comments on RLS policies and postponing restore of event triggers until the end.
  • Ensure pg_basebackup generates valid tar files.
  • pg_checksums skips tablespace subdirectories that belong to a different PostgreSQL major version
  • Several Windows compatibility fixes

This update also contains tzdata release 2020a for DST law changes in Morocco and the Canadian Yukon, plus historical corrections for Shanghai. The America/Godthab zone has been renamed to America/Nuuk to reflect current English usage ; however, the old name remains available as a compatibility link. This also updates initdb's list of known Windows time zone names to include recent additions.

For the full list of changes available, please review the release notes.

Updating

All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply shutdown PostgreSQL and update its binaries.

Users who have skipped one or more update releases may need to run additional, post-update steps; please see the release notes for earlier versions for details.

For more details, please see the release notes.

Links
Categories: Informatika

SQL Data Analysis 1.3

2020, May 11 - 02:00
SQL Data Analysis

See and understand your data using SQL Data Analysis. Supports PostgreSQL 8 to 12.

Benefits:
  • Connect to your PostgreSQL database, run your query, and visualize your data in seconds.
  • Analyze your data with intuitive drag & drop interface. No programming, just insights.
  • Cross database queries allow you to join a PostgreSQL data set with another database's data set (SQL Server, Oracle, MySQL, etc).
  • Flexible layouts allow you to combine multiple data views to best visualize your data.
  • Share and export your discoveries and insights to PDF, Excel, and HTML files.
Free trial

SQL Data Analysis is commercial software and a free trial is available. Learn more at https://www.yohz.com/sda_details.htm.

Categories: Informatika

pgMustard version 3

2020, May 6 - 02:00
pgMustard

pgMustard is a tool that gives performance advice based on PostgreSQL query plans. We're pleased to announce version 3.

Major improvements
  • Tip scoring – Each tip is now rated from 0-5, making it quicker and easier to determine the relative importance of issues.
  • Tip improvements – New tips for planning time and slow count operations. Improvements to most of our other tips too, meaning they are more likely to be relevant, and to give better advice.
  • Better subplan analysis – Improved some tricky cases around calculations between call sites and added more information to help. Thank you to Felix G for working with us on this!
  • Interface improvements – Major changes to our tree and reading pane to make problem-solving easier, not least for large query plans (with many operations or lots of nesting).
Requirements
  • JSON format query plans
  • PostgreSQL 9.6 and newer
  • Interface and advice are in English
  • A GitHub or Google account, for authentication on our hosted version (no installation or database access required)
  • Self-hosted option available, via Docker
Free trial

pgMustard is commercial software and has a free trial: https://www.pgmustard.com/

If you have any slow queries to speed up, we’d love to hear how you get on.

Categories: Informatika

Postgres Operator v1.5.0

2020, May 6 - 02:00

Zalando's DBaaS team has just released a new version of their Postgres Operator for Kubernetes. It now offers support for pgBouncer connection pooler which is beneficial when your app is scaled out to many pods, all holding connections. The pgBouncer deployment can simply be enabled in the Postgres cluster manifest and will help keeping connection count low and throughput high in such scenarios.

Databases can now be created with default (owner, reader, writer) roles and privileges to ease the setup for our users. It's also possible to specify database schemas and extensions in manifest to bootstrap.

New controller annotations can be used to run multiple operators next to each other without interfering. With this you can also easily detach a cluster from the control of the operator. Annotations injected to the Postgres resource can now be propagated to the StatefulSet i.e. to trigger downscaling of test clusters during quiet hours.

Our community is getting stronger. We receive valuable feedback and see increased activity of users providing more complex pull requests. This release in particular contains many feature highlights from external contributions:

  • Support for fully-speced sidecars to ease the integration with e.g. monitoring / logging solutions.
  • Additional volumes can be specified per cluster, e.g. for extra tablespaces, credentials, configuration files etc.
  • Support for custom TLS certificates
  • Better compatibility with OpenShift
  • Kubernetes events are emitted to the Postgresql resource to provide better feedback to the user

As always, the Postgres Operator is shipped with the latest Patroni and Spilo releases. Rolling updates of the docker image now check the health of all replicas and can be executed in lazy fashion until the next node rotation to reduce downtime.

Zalando is running several hundreds of Postgres clusters on top of Kubernetes via the operator and numbers keep growing steadily. Thanks to everyone involved, reporting bugs, suggesting improvements and contributing to the Postgres Operator!

Categories: Informatika

Crunchy PostgreSQL Operator 4.3: Multi-Kubernetes Cluster Deployments, Easier Customization/Installation, TLS, pgAdmin 4

2020, May 5 - 02:00

Crunchy Data is pleased to announce the release of the Crunchy PostgreSQL Operator 4.3, which automates and simplifies deploying and managing of open source PostgreSQL clusters on Kubernetes and other Kubernetes-enabled Platforms. Instructions for getting started with the PostgreSQL Operator can be found here:

https://access.crunchydata.com/documentation/postgres-operator/latest/quickstart/

This release makes it possible to deploy PostgreSQL across Kubernetes clusters in a multi-PostgreSQL Operator setup. There are also significant improvements to the ability to easily customize PostgreSQL clusters that are managed by the PostgreSQL Operator, from infrastructure configuration (CPU, RAM, PVC size) to PostgreSQL configuration.

Major features of the 4.3 release include:

For a full list of features, including detailed descriptions of these changes, please see the release notes.

Links
Categories: Informatika

arm64 on apt.postgresql.org

2020, May 4 - 02:00
arm64 on apt.postgresql.org

The apt.postgresql.org repository has been extended to cover the arm64 architecture.

HUAWEI Cloud Services donated a arm64 build host with enough resources to build the arm64 packages at the same speed as the existing amd64, i386, and ppc64el architectures.

We are targeting Debian buster (stable), bullseye (testing), and sid (unstable), and Ubuntu bionic (18.04) and focal (20.04). To use the arm64 archive, just add the normal sources.list entry:

deb https://apt.postgresql.org/pub/repos/apt buster-pgdg main Ubuntu focal

At the same time, I've added the next Ubuntu LTS release to apt.postgresql.org: focal (20.04). It ships amd64, arm64, and ppc64el binaries.

deb https://apt.postgresql.org/pub/repos/apt focal-pgdg main Old PostgreSQL versions

Many PostgreSQL extensions are still supporting older server versions that are EOL. For testing these extension, server packages need to be available. I've built packages for PostgreSQL 9.2+ on all Debian distributions, and all Ubuntu LTS distributions. 9.1 will follow shortly.

This means people can move to newer base distributions in their .travis.yml, .gitlab-ci.yml, and other CI files.

Categories: Informatika

pg_probackup 2.3.0 has been released

2020, April 30 - 02:00

pg_probackup is a utility to manage backup and recovery of PostgreSQL database cluster. It is designed to perform periodic full and incremental page-level backups of the PostgreSQL instance that enable you to restore the server in case of a failure.

Notable changes since pg_probackup 2.2.7

New features:

  • The --status option can be used with the delete command to remove all backups with the specified status. Requested by Stepan Santalov. Contributed by Victor Spirin.
  • The --no-sync flag can be used with backup, restore, and archive-push commands to disable syncing of copied files to the underlying storage.
  • The --note option allows to add a text note of size up to 1KB to the backup metadata when running backup and set-backup commands. Contributed by Victor Spirin.
  • Multi-timeline incremental chains are now supported. The timeline number of an incremental backup can differ from the parent timeline number, but only if it is possible to determine (using WAL archive) that the child timeline descends from the parent timeline.
  • You can now set PostgreSQL parameters primary_slot_name and primary_conninfo during restore using the -S | --primary-slot-name and --primary-conninfo options, respectively. Requested by Yuri Kurenkov.
  • Major revamp of the archive-push command:
  • Multi-threading support is added via the -j | --threads option.
  • Batch processing is added via the --batch-size option.
  • In the remote mode, checksums are now computed on a remote agent.
  • Major revamp of the archive-get command:
  • Multi-threading support is added via the -j | --threads option.
  • WAL prefetching is added via the --batch-size option. The default directory with prefetched WAL segments is PGDATA/pg_wal/pbk_prefetch. You can change this location using the --prefetch-dir option.
  • Partial WAL files produced by pg_receivewal program are now recognized and used if the corresponding full WAL segment is missing. Reported by Artem Dolgih.

Bugfixes:

  • Enabled logging info file should not break archiving anymore. Reported by Artem Dolgih.
  • The add-instance command no longer implicitly sets the --remote-proto and --remote-host parameters in the instance configuration when adding a remote PostgreSQL instance into the backup catalog.
  • When taking a backup in the ARCHIVE mode, pg_probackup now waits for the segment containing the START LSN, not the previous segment. Reported by Mikhail Kulagin.
  • The expire-time attribute is now inherited during merge.
  • Setting session parameters via the PGOPTIONS environment variable during backup now does not cause corruption of backup meta information.

Improvements:

  • The speed of restore from incremental chain is greatly improved. In some cases, by an order of magnitude. Reported and tested by Alex Ignatov.
  • The speed of merge, especially merge of several backups at a time, is greatly improved. Reported by Rostislav Pochevalov.
  • The speed of remote backup in PAGE and PTRACK modes is greatly improved.
  • You can now delete a backup even if there is no space left on device. Reported by Stepan Santalov.
  • Hidden files are now ignored during backup.
  • Now it is explicitly forbidden to restore a backup using an older pg_probackup version. Contributed by Dmitriy Kuzmin.
Links & Credits

pg_probackup is an open source tool developed by Postgres Professional under Postgres license. Main contributors are Artur Zakirov, Grigory Smolkin, Aleksey Kondratov and Anastasia Lubennikova. pg_probackup can be downloaded at https://github.com/postgrespro/pg_probackup.

Categories: Informatika

pgagroal 0.6.0

2020, April 28 - 02:00

The pgagroal community is happy to announce version 0.6.0.

New features

  • Transport Layer Security (TLS) v1.2+ support
  • Ability to set a minimum pool size
  • Authentication timeout setting for slow clients
  • Added a setting to control which pipeline to use

Plus various improvements and bug fixes.

pgagroal

pgagroal is a high-performance protocol-native connection pool for PostgreSQL.

Features

  • High performance
  • Connection pool
  • Limit connections for users and databases
  • Prefill support
  • Remove idle connections
  • Perform connection validation
  • Enable / disable database access
  • Graceful / fast shutdown
  • Transport Layer Security (TLS) v1.2+ support
  • Daemon mode
  • User vault

Learn more on our web site or GitHub. Follow on Twitter.

pgagroal is released under the 3-clause BSD license, and is sponsored by Red Hat.

Categories: Informatika

PgBouncer 1.13.0 released

2020, April 27 - 02:00

PgBouncer 1.13.0 is out. This release contains a variety of minor enhancements and fixes, including a new tcp_user_timeout setting, updated default TLS settings, and new systemd integration. See

https://www.pgbouncer.org/2020/04/pgbouncer-1-13-0

for more information, the detailed changelog, and download links.

PgBouncer is a lightweight connection pooler for PostgreSQL.

Categories: Informatika

Swarm64 DA 4.0: Now accelerates PostgreSQL JOINs, text filtering. FPGA support is optional.

2020, April 27 - 02:00

Swarm64 DA 4.0 is now available, a PostgreSQL extension that accelerates query and data loading performance in PostgreSQL 11 and higher.

Here are the release 4.0 highlights:

  • We’ve tripled the acceleration effect on PostgreSQL, mainly by adding additional parallelism and support for SQL JOINs acceleration.
  • FPGA support is now optional; you can use Swarm64 DA extensions on any hardware (with OR without an FPGA).
  • Postgres text filtering is now accelerated.
  • We patched pg_dump to backup and restore foreign table (FDW) data.

For more info...

Categories: Informatika

Announcing the Release of repmgr 5.1

2020, April 13 - 02:00

Oxford, United Kingdom - April 13, 2020

2ndQuadrant is proud to announce the release of repmgr 5.1. This major release includes several important enhancements.

repmgr enhances and complements the built-in replication capabilities in PostgreSQL and is the most popular tool for PostgreSQL replication and failover management. Repmgr makes it easy to set up and manage standby servers, check replication status, and perform administrative tasks such as switchover operations. The repmgrd daemon provides automatic failover capability to maximize database uptime, and can easily be integrated with other tools such as PgBouncer for high application availability.

repmgr 5.1 introduces an important compatibility change to the repmgr standby clone: the --recovery-conf-only option has been updated to --replication-conf-only.

In addition, repmgr 5.1 removes the requirement that the repmgr user is a database superuser, as far as possible. In theory, repmgr can be operated with a standard database user for managing the repmgr database, and a separate replication user for managing replication connections (and replication slots, if these are in use). Some operations will still require superuser permissions, e.g. for issuing a CHECKPOINT as part of a switchover operation; in this case, a valid superuser should be provided with the -S/--superuser option.

For a detailed list of all changes, please read the complete release notes here.

Upgrading to this version is highly recommended for all repmgr users. Upgrade instructions are available here.

Packages and installation documentation are available via 2ndQuadrant’s public RPM and APT repositories from 2ndQuadrant here.

Source files can be downloaded here and installation instructions are available here.

repmgr is distributed under GPL v3.

For more information, please send an email to info@2ndQuadrant.com

Categories: Informatika

Announcing "common" YUM repository

2020, April 7 - 02:00

The community PostgreSQL YUM repository does not just include PostgreSQL packages, but also some extensions which depend on a specific PostgreSQL version (e.g. PostGIS.), packages in the PostgreSQL world which can be used against some (or all) PostgreSQL versions (e.g. pgAdmin4), and the supportive packages for those extensions (e.g. Proj, GeOS).

Until yesterday, all of these packages were contained inthe same directory for each OS / PostgreSQL combination. This increased both build time and the disk space required.

So, I decided to merge the “common” packages (packages like pgAdmin4 and GEOS as described above) into one single repository.

Yesterday I released new repo RPMs (42.0-9) which introduce 3 new common repositories:

  • pgdg-common : Includes all of the “common” RPMs. Enabled by default.
  • pgdg-common-testing : testing repo for the common RPMs. Disabled by default, and please do not use it in production.
  • pgdg-common-srpm-testing: SRPMs for the packages in the common testing repo.

I will add a pgdg-common-srpms repository later on.

What to do now?
  • If you are using the default repo file (without editing it), a yum/dnf update will automatically update the new repo configuration file. No additional action required. This applies to the majority of our user base.

  • If you have manually edited the repo file, installing the new repo RPM will not overwrite it . Instead, it will create a new file ending with .rpmnew. You will need to merge changes from that file to the .repo file.

FAQ:
  • What happens when I don’t update the repo file?

Existing installations will continue running, and you will still receive “non-common” updates, in particular updates to the main PostgreSQL packages. However, new installations will fail when they need the common packages.

  • Will you release a separate repo RPM for the common repo?

No. That will cause more issues.

  • Did you really have to do this change?

Yes, as explained above.

  • “Package foobar does not exist in the repos. Did you remove it?”

I moved them to the common repository. Please update the repo file as described above.

  • How can I get more support?

Please send an email to pgsql-pkg-yum@lists.postgresql.org , or submit an issue in the community issue tracker: https://redmine.postgresql.org/projects/pgrpms/issues

Categories: Informatika

PostgreSQL JDBC 42.2.12 Released

2020, April 1 - 02:00

The JDBC team has released version 42.2.12

We have released 42.2.12 to correct regressions in this version: Specifically - PR 1729 was reverted as this is a breaking change - PR 1719 has been reverted as it introduced errors in the PgType Cache

We suggest not using 42.2.11

JDBC Team

Categories: Informatika

PostgreSQL Community Code of Conduct Committee Annual Report for 2019

2020, April 1 - 02:00

The PostgreSQL Community Code of Conduct Committee has delivered their Annual Report summarizing the complaints received and actions taken in the calendar year 2019.

All complaints and actions are anonymized to protect the identities of all parties involved.

You can view a copy of the report here:

https://www.postgresql.org/about/policies/coc/reports/2019/

Categories: Informatika

Announcing apt-archive.postgresql.org

2020, March 24 - 01:00

Users had often asked where they could find older versions of packages from apt.postgresql.org. I had been collecting these since about April 2013, and in July 2016, I made the packages available via an ad-hoc URL on the repository master host, called "the morgue". There was little repository structure, all files belonging to a source package were stuffed into a single directory, no matter what distribution they belonged to. Besides this not being particularly accessible for users, the main problem was the ever-increasing need for more disk space on the repository host. We are now at 175 GB for the archive, of which 152 GB is for the morgue.

Our friends from yum.postgresql.org have had a proper archive host (yum-archive.postgresql.org) for some time already, so it was about time to follow suit and implement a proper archive for apt.postgresql.org as well, usable from apt.

So here it is: apt-archive.postgresql.org

The archive covers all past and current Debian and Ubuntu distributions. The apt sources.lists entries are similar to the main repository, just with "-archive" appended to the host name and the distribution:

deb https://apt-archive.postgresql.org/pub/repos/apt DIST-pgdg-archive main deb-src https://apt-archive.postgresql.org/pub/repos/apt DIST-pgdg-archive main

The oldest PostgreSQL server versions covered there are 8.2.23, 8.3.23, 8.4.17, 9.0.13, 9.1.9, 9.2.4, 9.3beta1, and everything newer.

Some example:

$ apt-cache policy postgresql-12 postgresql-12: Installed: 12.2-2.pgdg+1+b1 Candidate: 12.2-2.pgdg+1+b1 Version table: *** 12.2-2.pgdg+1+b1 500 500 http://apt.postgresql.org/pub/repos/apt sid-pgdg/main amd64 Packages 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 100 /var/lib/dpkg/status 12.2-2.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12.2-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12.1-2.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12.1-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12.0-2.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12.0-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12~rc1-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12~beta4-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12~beta3-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12~beta2-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages 12~beta1-1.pgdg+1 500 500 https://apt-archive.postgresql.org/pub/repos/apt sid-pgdg-archive/main amd64 Packages

Because this is hosted on S3, browsing directories is only supported indirectly by static index.html files, so if you want to look at some specific URL, append "/index.html" to see it.

The archive is powered by a PostgreSQL database and a bunch of python/shell scripts, from which the apt index files are built.

Archiving old distributions

I'm also using the opportunity to remove some long-retired distributions from the main repository host. The following distributions have been moved over:

  • Debian etch (4.0)
  • Debian lenny (5.0)
  • Debian squeeze (6.0)
  • Ubuntu lucid (10.04)
  • Ubuntu saucy (13.10)
  • Ubuntu utopic (14.10)
  • Ubuntu wily (15.10)
  • Ubuntu zesty (17.04)
  • Ubuntu cosmic (18.10)

They are available as "DIST-pgdg" from the archive, e.g. squeeze:

deb https://apt-archive.postgresql.org/pub/repos/apt squeeze-pgdg main deb-src https://apt-archive.postgresql.org/pub/repos/apt squeeze-pgdg main
Categories: Informatika

pgagroal 0.5.0

2020, March 17 - 01:00
pgagroal 0.5.0

March 17, 2020.

The pgagroal community is happy to announce version 0.5.0.

New features

  • SCRAM-SHA-256 support
  • Log connections
  • Cancel shutdown
  • Enable / disable database access
  • Allow user connections during prefill

Plus various improvements and bug fixes.

pgagroal

pgagroal is a high-performance protocol-native connection pool for PostgreSQL.

Features

  • High performance
  • Connection pool
  • Limit connections for users and databases
  • Prefill support
  • Remove idle connections
  • Perform connection validation
  • Enable / disable database access
  • Graceful / fast shutdown
  • Daemon mode
  • User vault

Learn more on our web site or GitHub. Follow on Twitter.

pgagroal is released under the 3-clause BSD license, and is sponsored by Red Hat.

Categories: Informatika

check_pgbackrest 1.8 has been released

2020, March 16 - 01:00

Mons, Belgium, March 16, 2020

check_pgbackrest is designed to monitor pgBackRest backups from Nagios, relying on the status information given by the info command.

It allows to monitor the backups retention and the consistency of the archived WAL segments.

Changes in check_pgbackrest 1.8
  • Change output of missing archives. The complete list is now only shown in --debug mode (suggested by Guillaume Lelarge).
  • Add --list-archives argument to print the list of all the archived WAL segments.
Links & Credits

check_pgbackrest is part of the Dalibo Labs initiative. It is mainly developed by Stefan Fercot. This is an open project, licensed under the PostgreSQL license. Any contribution to improve it is welcome.

Links:

  • [Download]: https://github.com/dalibo/check_pgbackrest/releases
  • [Support]: https://github.com/dalibo/check_pgbackrest/issues
Categories: Informatika

Pages

Theme by me