PostreSQL.org

Oxford, United Kingdom - 22 October, 2020

2ndQuadrant is proud to announce the release of repmgr 5.2.0. This major release adds support for PostgreSQL 13 and includes several general improvements, important enhancements, and bug fixes.

repmgr is the most popular tool for PostgreSQL replication and failover management that enhances the built-in replication capabilities in PostgreSQL. It simplifies daily management of standby servers and allows smooth execution of administrative tasks such as switchover operations. The automatic failover capability of repmgr allows maximum database uptime and can be combined with other tools such as PgBouncer for high availability.

repmgr 5.2.0 adds the new --verify-backup option to run PostgreSQL's pg_verifybackup utility after cloning a standby to verify the integrity of the copied data (PostgreSQL 13 and later).

Furthermore, repmgr 5.2.0 enhances the failover_validation_command with additional parameters and the configuration option always_promote that is used to control whether a node should be promoted if the repmgr metadata is not up-to-date.

5.2.0 also removes the support for PostgreSQL 9.3, which was designated EOL in November 2018.

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

Recently, the acquisition of 2ndQuadrant by EDB was announced. This resulted in the Core Team’s membership consisting of a majority of members being employed by EDB.

There has long been an unwritten rule that there should be no more than 50% of the membership of the Core Team working for the same company. As a result, there has been a lively ongoing discussion within the core team on how to best resolve this issue. For obvious reasons we do not want to rush into making changes.

We are aware that this has taken longer than expected, and apologise for any concern this may have caused in the community. Rest assured we are actively working to resolve the issue in a way that benefits the project, and will announce details as soon as possible once they are finalised.

Unfortunately the fixes in 42.2.17 weren't quite enough to fix the problem with gssEncMode. 42.2.18 has (hopefully) fixed them. See the details in the release notes

The pgAdmin Development Team is pleased to announce pgAdmin 4 version 4.27. This release of pgAdmin 4 includes 28 bug fixes and new features. For more details please see the release notes.

pgAdmin is the leading Open Source graphical management tool for PostgreSQL. For more information, please see the website.

Notable changes in this release include:

• Added Macro support.
• Added support to view trigger function under the respective trigger node.
• Allow user to change the database connection from an open query tool tab.
• Added support to ignore the owner while comparing objects in the Schema Diff tool.
• Merged the latest code of 'pgcli' used for the autocomplete feature.
• Fixed invalid literal issue when fetching dependencies for Materialized View.
• Fixed an issue where schema diff is showing identical table as different due to default vacuum settings.
• Ensure that the user should be able to change the start value of the existing sequence.
• Fixed an issue where the query tool is not fetching more than 1000 rows for the table does not have any primary key.
• Fixed an issue where 'Rows X' column values were not visible properly for Explain Analyze in Dark theme.
• Fixed an issue where file extension is stripped on renaming a file.

Builds for Windows and macOS are available now, along with a Python Wheel, Docker Container, RPM, DEB Package, and source code tarball from the tarball area.

Grenoble, France - October 12th, 2020

Ora2Pg 21.0 released

Version 21.0 of Ora2Pg, a free and reliable tool used to migrate an Oracle database to PostgreSQL, has been officially released and is publicly available for download.

This release fix several issues reported since last release and adds several new features and improvements.

New features and improvements

• Add clause OVERRIDING SYSTEM VALUE to INSERT statements when the table has an IDENTITY column.
• Considerably increase the speed to generate the report about the migration assessment, especially for database with huge number of objects.
• Reduce time passed in the progress bar. Following the number of database objects we were spending too much time in refreshing the progress bar.
• Add number of identity columns in migration assessment report.
• Make assessment details report initially hidden using HTML5 tags details+summary
• Improve speed of BLOB/CLOB data export. Oracle recommends reading from and writing to a LOB in batches using a multiple of the LOB chunk size. This chunk size defaults to 8k (8192). Recent tests show that the best performances can be reach with higher value like 512K or 4Mb.
• Add progress bar when --oracle_speed is use in single process mode.
• Automatically activate USER_GRANTS when the connection user has no DBA privilege. A warning is displayed.
• Complete port to Windows by using the Windows separator on stdout redirection into a file at ora2pg command line call and improve ora2pg_scanner port on Windows OS.
• Add rewrite of MySQL JOIN with WHERE clause instead of ON.
• Add MGDSYS (Oracle E-Business Suite) and APEX_040000 to the list of schemas excluded from the export.
• Supply credentials interactively when a password is not defined in the configuration file. Need the installation of a new Perl module Term::ReadKey.
• Add supports oracle connections "as sysdba" with username "/" and an empty password to connect to a local oracle instance.
• Add translation of PRIVATE TEMPORARY TABLE from Oracle 18c into PostgreSQL basic temporary table, only the default behavior for on commit change.

New command line options

• Add new command line option to ora2pg_scanner: -b | --binpath DIR to set the full path to directory where the ora2pg binary stays. Might be useful only on Windows OS.
• Add -r | --relative command line option and PSQL_RELATIVE_PATH configuration directive. By default Ora2Pg use \i psql command to execute generated SQL files if you want to use a relative path following the script execution file enabling this option will use \ir. See psql help for more information.

New configuration directives

• NO_VIEW_ORDERING by default Ora2Pg try to order views to avoid error at import time with nested views. With a huge number of views this can take a very long time, you can bypass this ordering by enabling this directive.
• NO_FUNCTION_METADATA: force Ora2Pg to not look for function declaration. This will prevent Ora2Pg to rewrite function replacement call if needed. Do not enable it unless looking forward at function breaks other export.
• LOB_CHUNK_SIZE: see explanation in the new features and improvement list about BLOB/CLOB export speed improvement.
• ALTERNATIVE_QUOTING_REGEXP: to support the Alternative Quoting Mechanism ('Q' or 'q') for String Literals set the regexp with the text capture to use to extract the text part. The value of this directive can be a list of regexp separated by a semi colon. The capture part is mandatory in each regexp if you want to restore the string constant.

Backward compatibility changes

• Default for NO_LOB_LOCATOR is now 1 to benefit from LOB_CHUNK_SIZE performances gain.
• Enable schema compilation (COMPILE_SCHEMA set to 1) by default to speed up DDL extraction.
• Change the behavior of Ora2Pg with the parameters that follows a parameter with a default value. Ora2Pg used to change the order of the parameters function to put all parameters with a default value at end of the list which need a function call rewrite. This have been abandoned, any parameter without default value after a parameter with a default value will now be appended with DEFAULT NULL.

For a complete list of change see https://github.com/darold/ora2pg/blob/master/changelog

Thanks to all contributors, they are all cited in the changelog file.

Useful Links

• Website: http://www.ora2pg.com/
• Download1: https://github.com/darold/ora2pg/releases
• Download2: http://sourceforge.net/projects/ora2pg/
• Development: https://github.com/darold/ora2pg
• Changelog: https://github.com/darold/ora2pg/blob/master/changelog

• Documentation: http://www.ora2pg.com/documentation.html

• Global Temporary Tables for PostgreSQL extension: https://github.com/darold/pgtt

• BFILE for PostgreSQL extension: https://github.com/darold/external_file

About Ora2Pg

Ora2Pg is an easy and reliable tool to migrate from Oracle to PostgreSQL. It is developed since 2001 by Gilles Darold and can export most of the Oracle objects (table, view, materialized view, tablespace, sequence, indexes, trigger, grant, function, procedure, package, partition, data, blob, external table, etc.).

Ora2Pg works on any platform and is available under the GPL v3 license.

Docs, Download & Support at http://www.ora2pg.com/

Today, the PostgreSQL Community Code of Conduct Committee welcomes three new members:

Jeanette Bromage is a Principal DBA at Kira Systems. Prior to this, she took a three year break from managing databases to concentrate on AWS/Linux system administration. Jeanette has worked with various database technologies across different platforms for over twenty years, including a three year stint as a C programmer.

Fábio Telles Rodriguez is a Database Consultant and co-founder of Timbira, in Brazil. He is a co-organizer of both PGConf.Brazil and Brazilian PUG. He organizes and speaks in many other conferences in his country.

Anastasia Lubennikova is a Senior Developer at Postgres Professional and a PostgreSQL Global Development Group Contributor. She contributes to the PostgreSQL community as a core developer and speaker. As a part of her job, she also helps with mentoring and onboarding new developers.

Ilya Kosmodemiansky, who served on the initial Committee, is stepping down this year. We appreciate his involvement the past two years.

There will be a short transition period, ending October 31, 2020 to allow the transfer of information and responsibilities. The new term runs through September 30, 2021.

The continuing Committee members are:

Stacey Haysler (Chair) is the CFO and COO of PostgreSQL Experts, Inc., in Alameda, California. She is a PostgreSQL Global Development Group Contributor, and the President of the United States PostgreSQL Association (PgUS). She has worked as an organizer and conference staff for a number of conferences, both in North America and Europe, and is also a principal organizer of the San Francisco PostgreSQL Users’ Group.

Jonathan S. Katz is the Vice President of Platform Engineering at Crunchy Data, and lives in New York. He is a PostgreSQL Global Development Group Major Contributor focused on advocacy, the website, and releases, and also serves on the boards of the United States PostgreSQL Association & the PostgreSQL Community Association of Canada.

Carole Arnaud is an executive board member of Dalibo and team manager. She lives in Nantes, France. She was part of the PGDay France committee from 2015 to 2018, and has been a co-organizer of pgDay Paris since 2018.

Umair Shahid is a Member of the Marketing Leadership at EDB and is based in Islamabad, Pakistan. He serves as a member of PgUS User Group committee along with being the organizer for Islamabad and Dubai PostgreSQL Users' Groups.

The Committee is comprised of 4 women, 3 men, and 0 nonbinary individuals. No two members work at the same company.

We have again expanded our geographical diversity, which now includes our first member from South America. The specific country representation is:

• Brazil: 1
• France: 1
• Pakistan: 1
• Russian Federation: 1
• United Kingdom: 1
• United States: 2

The full list of Committee members is always available at: https://www.postgresql.org/about/policies/coc_committee/

The Committee can be contacted at coc@postgresql.org.

Memhive PostgreSQL acceleration with Persistent Memory (PMEM) is now available! Memhive PostgreSQL has been built on PMDK and accelerates storage and memory access using libpmem. Our benchmarking with Intel Optane PMEM has yielded impressive results!

Advantages of Memhive PostgreSQL:

• Scaling up performance: PMEM resident persistent cache, fast WAL and relational data files..
• Reduction in TCO: Lower DRAM and fast SSD capacity requirement.
• Easy upgrade: no change to client-side behavior, core business logic or on-disk layout.

More information:

Visit our website: https://www.memhive.io

Write to us at: info@memhive.io

Due to some small issues with the way GSS Encryption was implemented we have released 42.2.17. The major change is not to attempt a GSS Encrypted connection by default.

There were a number of small issues fixed:

• Avoid NullPointerException when receiving PGbox, PGcircle, PGline, PGlseg, PGpath, PGpoint, PGpolygon, and PGmoney PR 1873..
• The driver returns enum and jsonb arrays elements as String objects (like in 42.2.14 and earlier versions) PR 1879.
• PgTokenizer was ignoring last empty token PR #1882
• Remove osgi from karaf fixes Issue #1891 PR #1902

See the complete list of changes here

Thanks to everyone who contributed !

Crunchy Data is pleased to announce the release of the Crunchy PostgreSQL Operator 4.5, which automates and simplifies deploying and managing 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 several changes to the PostgreSQL Operator Monitoring solution, notably making it much easier to set up a turnkey PostgreSQL monitoring with the PostgreSQL Operator using the open source pgMonitor project.

pgMonitor combines insightful queries for PostgreSQL with several proven tools for statistics collection, data visualization, and alerting to allow one to deploy a turnkey monitoring solution for PostgreSQL. Now with support for Kubernetes environments, pgMonitor uses open source pgnodemx that allows one to get host-like information from the Kubernetes Pod a PostgreSQL instance is deployed within.

Major features of the 4.5 release include:

• Enhanced PostgreSQL Operator Monitoring
• Apply Custom Annotations to Managed Deployments, which helps with integrations with additional Kubernetes applications
• Customize pgBackRest and pgBouncer via ConfigMaps
• Support for the Kubernetes default storage class
• Support for PostgreSQL 13

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

Links

• Project Repo
• Download
• Documentation
• Tutorial
• Release Notes

Crunchy Data is proud to support the development and maintenance of the PostgreSQL Operator.

Yohz Software has released DB Doc 8.0, the PostgreSQL schema documentation tool, and is available for immediate download.

Changes in this version:

• Added support for PostgreSQL 13
• Added support for materialized views
• Updated the HTML noframes layout
• Updated the HTML preview window

DB Doc benefits:

• Document a PostgreSQL database in 5 simple steps
• Create documentation in HTML, XML, PDF, CHM, and MS Word formats. You can view the samples here
• View database statistics like the largest tables and indexes in each database
• Document layouts are fully customizable to suit your requirements
• Eliminate tedious and time-consuming manual documentation tasks
• Satisfy audit requirements by keeping complete and timely documentation
• View inter-object and inter-database dependencies in your documents
• Keep teams up to date by distributing timely and accurate documentation
• Supports PostgreSQL 8.3 and newer, without the need for any additional database drivers.
• Runs on Windows 7 to Windows 10

For more details about DB Doc, please visit the product page. DB Doc-related technical blogs are available here.

Hello All,

We're happy to announce the release of v1.10 of pgmetrics. Changes since the v1.9 release include:

• Support for Postgres 13
• Collect information from Citus and Microsoft Azure Hyperscale Citus (more info here [1])
• Support for CSV-format logs
• Support for processing multiple log files in one run
• Option to collect from all available databases of a cluster
• Option to specify lock timeout
• Various bug fixes

You can get the latest release from GitHub [2].

Thanks to all the people who pitched in with bug reports, suggestions and patches! Keep it coming!

About pgmetrics

pgmetrics is an open-source, zero-dependency, single-binary tool that can collect a lot of information and statistics from a running PostgreSQL server and display it in easy-to-read text format or export it as JSON or CSV for scripting, monitoring and automation.

Learn more at https://pgmetrics.io/, or see a sample report here [3].

pgmetrics is an open-source project of RapidLoop [4].

[1] https://pgmetrics.io/docs/citus.html [2] https://github.com/rapidloop/pgmetrics/releases [3] https://pgmetrics.io/docs/index.html#example [4] https://www.rapidloop.com

Regards, -Mahadevan

CYBERTEC is proud to announce the availability of Scalefield, a modern solution offering PostgreSQL-as-a-service for on-premise deployments and inhouse clouds.

Scalefield is based on Kubernetes and OpenShift and comes with:

clustering:

• automatic failover
• fully transparent clustering

storage options:

• CEPH: network storage
• SAN-storage
• local SSD storage

automatic monitoring:

• full Prometheus support
• out of the box support for Grafana/pgwatch2

integrated data sets:

• integrated GIS data sets
• SQL sample data

web interfaces:

• ready-to-use graphical user interface
• intuitive graphical user management
• ability to add PostgreSQL deployments easily

Scalefield is the ideal on premise solution for high availability PostgreSQL setups.

We also offer our solution to companies interested in building their own hosting offer.

More information & contact

Learn more about Scalefield on our website.

Contact our sales team for a personal demonstration or further information: sales@cybertec.at

Version 2.3.0 of the Foreign Data Wrapper for Oracle is out.

This release provides support for PostgreSQL v13.

There are some new parameters to work around problems and limitations and make your life better, see the release notes.

A new function oracle_execute() allows executing utility statements on Oracle; this requires updating the extension with

ALTER EXTENSION oracle_fdw UPDATE;

after installing the binaries.

Project page: http://laurenz.github.io/oracle_fdw/

Source repository: https://github.com/laurenz/oracle_fdw

Enjoy!

Yours,
Laurenz Albe
Cybertec | https://www.cybertec-postgresql.com

New milestone PostgresDAC release is out! Now with PostgreSQL 13 and RAD Studio 10.4.1 support

PostgresDAC is a direct access component suite for RAD Studio (Delphi and C++Builder)/FreePascal/Lazarus and PostgreSQL, EnterpriseDB, Amazon RDS, PostgresPro, and Heroku Postgres. Full changelog:

[!] v13 client libraries added [!] v13 dump & restore libraries (pg_dump.dll, pg_restore.dll) added [*] TPSQLTable.HasOIDs property removed as obsolete [*] Fix foCaseInsensitive in TPSQLDataset.Filter Download

You're welcome to download the PostgresDAC v3.9 right now at http://microolap.com/products/connectivity/postgresdac/download/ or login to your private area on our site at http://microolap.com/my/downloads/

Feedback

Please don't hesitate to ask any questions or report bugs with our Support Ticketing system available at http://www.microolap.com/support/

The PostgreSQL Global Development Group today announced the release of PostgreSQL 13, the latest version of the world’s most advanced open source database.

PostgreSQL 13 includes significant improvements to its indexing and lookup system that benefit large databases, including space savings and performance gains for indexes, faster response times for queries that use aggregates or partitions, better query planning when using enhanced statistics, and more.

Along with highly requested features like parallelized vacuuming and incremental sorting, PostgreSQL 13 provides a better data management experience for workloads big and small, with optimizations for daily administration, more conveniences for application developers, and security enhancements.

"PostgreSQL 13 showcases the collaboration and dedication of our global community in furthering the abilities of the world's most advanced open source relational database," said Peter Eisentraut, a PostgreSQL Core Team member. "The innovations that each release brings along with its reputation for reliability and stability is the reason why more people choose to use PostgreSQL for their applications."

PostgreSQL, an innovative data management system known for its reliability and robustness, benefits from over 25 years of open source development from a global developer community and has become the preferred open source relational database for organizations of all sizes.

Continued Performance Gains

Building on work from the previous PostgreSQL release, PostgreSQL 13 can efficiently handle duplicate data in B-tree indexes, the standard database index. This lowers the overall space usage that B-tree indexes require while improving overall query performance.

PostgreSQL 13 introduces incremental sorting, where sorted data from an earlier step in a query can accelerate sorting at a later step. Additionally, PostgreSQL can now use the extended statistics system (accessed via CREATE STATISTICS) to create improved plans for queries with OR clauses and IN/ANY lookups over lists.

In PostgreSQL 13, more types of aggregate and grouping set queries can leverage PostgreSQL’s efficient hash aggregation functionality, as queries with large aggregates do not have to fit entirely into memory. Queries with partitioned tables have received a performance boost, as there are now more cases where partitions can be pruned and where partitions can be directly joined.

Administration Optimizations

Vacuuming is an essential part of PostgreSQL administration, enabling the database to reclaim storage space after rows are updated and deleted. This process can also present administrative challenges, though prior PostgreSQL releases have done work to ease the overhead of vacuuming.

PostgreSQL 13 continues to improve the vacuuming system with the introduction of parallelized vacuum for indexes. In addition to the vacuuming performance benefits it offers, the use of this new feature can be tuned to specific workloads as administrators can select the number of parallel workers to run. In addition to these performance benefits, data inserts can now trigger the autovacuum process.

Replication slots, which are used to prevent write-ahead logs (WAL) from being removed before they are received by a replica, can be tuned in PostgreSQL 13 to specify the max number of WAL files to retain and help avoid out-of-disk errors.

PostgreSQL 13 also adds more ways an administrator can monitor database activity, including referencing WAL usage statistics from EXPLAIN, the progress of streaming base backups, and the progress of the ANALYZE commands. Additionally, the integrity of the output of the pg_basebackup command can be checked using the new pg_verifybackup command.

Application Development Conveniences

PostgreSQL 13 makes it even easier to work with PostgreSQL data types coming from different data sources. This release adds the datetime() function to its SQL/JSON path support, which converts valid time formats (e.g. ISO 8601 strings) to PostgreSQL-native types. Additionally, the UUID v4 generation function, gen_random_uuid(), is now available without having to install any extensions.

PostgreSQL’s partitioning system is more flexible, as partitioned tables fully support logical replication and BEFORE row-level triggers.

The FETCH FIRST syntax in PostgreSQL 13 is now expanded to include the WITH TIES clause. When specified, WITH TIES includes any rows that, based on the ORDER BY clause, "tie" with the last row in the result set.

Security Enhancements

PostgreSQL’s extension system is a key component of its robustness as it allows developers to expand its functionality. In previous releases, new extensions could only be installed by a database superuser. To make it easier to take advantage of PostgreSQL’s extensibility, PostgreSQL 13 adds the concept of a "trusted extension," which allows database users to install extensions that a superuser marks as "trusted." Certain built-in extensions are marked as trusted by default, including pgcrypto, tablefunc, hstore, and more.

For applications that require secure authentication methods, PostgreSQL 13 allows for clients to require channel binding when using SCRAM authentication, and the PostgreSQL foreign data wrapper (postgres_fdw) can now use certificate-based authentication.

About PostgreSQL

PostgreSQL is the world's most advanced open source database, with a global community of thousands of users, contributors, companies and organizations. Built on over 30 years of engineering, starting at the University of California, Berkeley, PostgreSQL has continued with an unmatched pace of development. PostgreSQL's mature feature set not only matches top proprietary database systems, but exceeds them in advanced database features, extensibility, security, and stability.

Press Release Translations

• Chinese
• French
• German
• Hebrew
• Indonesian
• Japanese
• Korean
• Polish
• Portuguese
• Russian
• Spanish

Links

• Download
• Release Notes
• Press Kit
• Security Page
• Versioning Policy
• Follow @postgresql on Twitter

The pgagroal community is happy to announce version 0.9.0.

New features

• Transaction pooling
• Huge page support
• Unix Domain Socket support

Plus various improvements.

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
• Authentication query support
• Failover support
• 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.

The new maintenance release for pg_chameleon adds the support for reduced lock if MySQL engine is transactional, thanks to rascalDan

The initialisation process now checks whether the engine for the table is transactional and runs the initial copy within a transaction. The process still requires a FLUSH TABLES WITH READ LOCK but the lock is released as soon as the transaction snapshot is acquired. This improvement allows pg_chameleon to run against primary databases with minimal impact during the init_replica process.

The python-mysql-replication requirement is now changed to version >=0.22 which adds the support for PyMySQL >=0.10.0.

HighGo Software Inc. (Canada) is pleased to announce the GitHub community release of orc_fdw v1.1.0.

Browse to the github release URL to access v1.1.0 release: ORC FDW v1.1.0 Release

Feature Enhancements:

• Support added for joins between ORC foreign tables
• Predicate pushdown handling added for boolean, const and operator evaluations
• Target list pushdown for non-aggregate queries
• Improved import schema functionality

and ...

• Miscellaneous bug fixes

github

github: https://github.com/HighgoSoftware/orc_fdw/

Upcoming

In the meantime, we are continuously working on adding more features to this FDW. We look forward to your feedback which will help us improve it significantly. Part of the future enhancements is to add DML support which will be added in a future version.

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.4
• 4.0.11
• 3.7.16
• 3.6.23
• 3.5.27

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.

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.4
• 4.0.11
• 3.7.16
• 3.6.23
• 3.5.27

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.