You are here

PostreSQL.org

Subscribe to PostreSQL.org feed
PostgreSQL news
Updated: 12 hours 39 min ago

Announcing the release of AgensGraph 1.3

2018, April 25 - 02:00

The AgensGraph Development Team are pleased to announce the release of AgensGraph v1.3.

AgensGraph is a new generation multi-model graph database based on PostgreSQL for highly connected data.
AgensGraph offers the graph analysis environment in which users can write, edit, and execute
SQL and Cypher query together at the same time. AgensGraph comes along with PostgreSQL compatibility
and PostgreSQL Extensions. With AgensGraph, a PostgreSQL for graph database, PostgreSQL users are free
from the pain of data migration and easily develop services which provide advanced data analysis.

This release of AgensGraph v1.3 includes the bug fixes and of course, many improvements.
For more details please see the release notes.

Major Improvements and Bug Fixes:
  • Improvements
  • Enhanced Query Plan Performance
  • Supports for More Cypher Expressions
  • Enhanced Supports for External Module
  • Improved Usability
  • Optimized Memory Usage (v1.3.1)
  • Bug Fixes
  • Fixed Bugs Related to Using Multiple Cypher Keywords
  • Fixed Memory Leak in Loading Data
  • Fixed Bugs Related to Vertex Reference
The new version is immediately available for download.
Categories: Informatika

Pgpool-II 3.7.3, 3.6.10, 3.5.14, 3.4.17 and 3.3.21 are now officially released.

2018, April 17 - 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:

  • 3.7.3
  • 3.6.10
  • 3.5.14
  • 3.4.17
  • 3.3.21

These are the latest stable minor versions of each major versions of Pgpool-II. 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

pgAdmin 4 v3.0 released!

2018, April 13 - 02:00

The pgAdmin Development Team are pleased to announce pgAdmin 4 version 3.0. This release of pgAdmin 4 includes over 100 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:

  • The desktop runtime now runs as a system tray application and utilises the browser on the system to display pgAdmin. This resolves numerous bugs and issues caused by QtWebKit/QtWebEngine.
  • Data can now be sorted in edit mode in the Query Tool.
  • Keyboard navigation with configurable shortcuts for many operations has been added to allow use of pgAdmin without a mouse.
  • Dashboard tables and charts can be enabled/disabled.
  • Server and database statistics, functions, partitions, external tables and EXPLAIN are now supported on Greenplum.
  • Support for pg_service.conf files has been added.
  • The Docker Container distribution is vastly slimmed down, having move to Alpine Linux with Gunicorn to host the pgAdmin web application.

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

RPM and DEB packages are expected to be available on the postgresql.org repositories within the next few days.

Categories: Informatika

Announcing the release of Citus 7.3

2018, April 5 - 02:00

The Citus 7.3 extension to Postgres now includes broader SQL coverage, support for TopN extension, and integration with Tableau. Developers building real-time analytics dashboards and multi-tenant applications will benefit the most.

You can find more information in the Citus 7.3 release notes.

Citus 7.3 is compatible with PostgreSQL 9.6 and 10. You can try Citus 7.3 by following the download instructions or one-click deploy through the Citus Cloud console.

Categories: Informatika

Database .NET v24.5 released

2018, March 31 - 02:00

Database .NET v24.5 is an innovative, powerful and intuitive multiple database management tool. (Full support for PostgreSQL 8/9/10)

Free, All-In-One, Portable, Single executable file and Multi-language.

Major New features from version 23.2 to 24.5:

  • Startup, closing data import and export performance improvements
  • Added support for macaddr8 in PostgreSQL 10
  • Added Description for connections
  • Added DateTime default value Selector
  • Added Displaying a progress indicator in a taskbar button
  • Added Duplicating Tables
  • Added Generating UPDATE and DELETE statements from results
  • Added Generating the command-line to Clipboard
  • Added Restoring recently closed tabs
  • Added Copying Script to Clipboard
  • Improved Query Builder
  • Improved Query Reverse Engineering
  • Improved Database Diagram
  • Improved Visual Execution Plan
  • Improved Table Designer
  • Improved Data Editor
  • Improved SQL Editor
  • Improved AutoComplete and IntelliSense
  • Improved Data Import and Export
  • Improved Connection List
  • Improved Command-Line
  • ...and more
The new version is immediately available for download.
Categories: Informatika

pgBackRest 2.01 Released

2018, March 28 - 02:00

March 28, 2018: Crunchy Data announces the release of pgBackRest 2.01, the latest version of the simple, reliable backup and restore system that can seamlessly scale up to the largest databases and workloads.

pgBackRest 2 brings significant improvements to performance. The pgbackrest executable and asynchronous archive-push command are now written in C, which significantly reduces the time required for PostgreSQL to acknowledge WAL segments pushed by the asynchronous process.

pgBackRest supports a robust set of features for managing your backup and recovery infrastructure, including: parallel backup/restore, full/differential/incremental backups, delta restore, parallel asynchronous archiving, per-file checksums, page checksums (when enabled) validated during backup, compression, partial/failed backup resume, backup from standby, tablespace and link support, backup expiration, local/remote operation via SSH, and more.

You can download pgBackRest from the PostgreSQL Yum Repository, the PostgreSQL APT Repository, or from the official pgBackRest website: https://pgbackrest.org.

Links New Features pgbackrest executable is now written in C

pgBackRest commands can now be written in C or embedded Perl. This allows performance-sensitive commands (like asynchronous archive-push) to be implemented in C with significant performance benefits. Most commands are still written in Perl but are loaded only when required to reduce startup time.

Performance Improvements for “archive-push”

The archive-push command is now partially coded in C and allows the PostgreSQL archive_command to run significantly faster when processing status messages from the asynchronous archive process. Testing has shown that the startup time for asynchronous archive-push is up to 40 times faster, enabling more WAL logs to be archived per day.

S3 Performance Improvements

Performance improvements have been made to the S3 list and delete commands.

Categories: Informatika

Announcing the release of TopN PostgreSQL extension

2018, March 27 - 02:00

Citus Data, is excited to announce the release of TopN, an open source PostgreSQL extension that returns the top values in a database according to some criteria. The TopN extension enables you to serve instant and approximate results to TopN queries. With the help of a very efficient approximation algorithm, TopN is able to materialize top values according to some criteria and incrementally update these top values, or merge them on-demand across different time intervals.

With TopN, you can:

  • Materialize your TopN results and update them incrementally.
  • Calculate TopN results approximately and very quickly.
  • Benefit the rich feature set of JSONB for your TopN datasets.

TopN is developed and maintained by Citus Data.

You can reach further information here and open source repository here. Please, do not hesitate to contact us via citusdata.com for further inquiries.

Categories: Informatika

Introducing brand-new dbForge Studio for PostgreSQL, a powerful IDE for working with PostgreSQL databases

2018, March 22 - 01:00

Devart announced the first release of dbForge Studio for PostgreSQL that allows to manage and develop database objects in PostgreSQL. This new IDE offers many robust features like Code Completion, Object Explorer and Data Editor which help users create, develop and execute queries as well as edit and adjust the code to their requirements in a convenient and user-friendly interface.

In the first version, dbForge Studio for PostgreSQL offers the following key features:

1) Code Completion enables users to save their time and enhance the code quality while writing SQL queries with the help of numerous helpful functionalities like:

• List Members • Parameter Info • Quick Info • Complete Word

2) Object Explorer with expandable objects allows users to navigate through the object tree, find any PostgreSQL objects of interest and perform the following tasks:

• Retrieve data from a table to present on a single SQL document • Truncate a table • Select Properties to view specific information on objects

3) Data Editor simplifies the process of editing PostgreSQL table data offering many handy capabilities:

• Editing data similar to Google Sheets and MS Excel or in the card view mode • Managing the settings of tables, such as adjusting column width • Setting either paginal or auto-search mode by default • Changing colors and formats of rows and cells using a rich set of fonts and sizes • Providing predefined data type formats so that users can select the most suitable for their needs

For more information about dbForge Studio for PostgreSQL, please visit https://www.devart.com/dbforge/postgresql/studio/

About Devart

Devart, a Czech software vendor, is one of the leading developers of database tools and administration software, ALM solutions, data providers for various database servers, data integration and backup solutions. The company also implements Web and Mobile development projects.

Learn more about Devart at https://www.devart.com.

Categories: Informatika

Announcing the Release of pglogical 2.2

2018, March 20 - 01:00

Oxford, United Kingdom - March 20, 2018

2ndQuadrant is proud to announce the release of pglogical 2.2, the next generation in logical replication for PostgreSQL. Implemented entirely as a PostgreSQL extension, pglogical is a logical replication system that serves as a highly efficient method of replicating data as an alternative to physical replication.

This release presents important enhancements and bug fixes including:

  • Fixed a race condition that could cause table synchronization to fail.
  • pglogical.alter_ subscription_synchronize() now removes synchronization info about orphaned tables.
  • Recreate replication slot on retry after table synchronization failure, which should improve table synchronization recovery after intermittent errors.
  • Report process identification based on log_line _prefix settings, making it easier to obtain pglogical messages from the server logs.
  • pglogical_create _subscriber no longer generates errors when run multiple times on the same provider.
  • Handle epoll_ctl failures cleanly to avoid internal error messages.
  • Improved memory management.

pglogical is supported by 2ndQuadrant, your diligent team of PostgreSQL experts.

Download and installation instructions are available here.

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

Categories: Informatika

Announcing general availability of Azure Database for PostgreSQL

2018, March 20 - 01:00

Azure Database for PostgreSQL is now Generally Available. Use the database engine you're familiar with, together with languages and frameworks of your choice - now as a secure managed service in the cloud.

Read more here and create an instance today.

Categories: Informatika

JDBC 42.2.2 Released

2018, March 16 - 01:00

The JDBC project is proud to announce the latest version 42.2.2. This release primarily fixes existing bugs including as well as updates documentation, including:

  • Documentation for server-side prepared statements
  • Support for generated keys for WITH queries missing RETURNING
  • Support for generated keys when INSERT/UPDATE/DELETE is followed by a comment
  • Fix incorrect results when a single-statement is used with different bind types
  • allowEncodingChanges should allow "SET client_encoding = ..."

and more.

For more details, please visit the changelog at https://jdbc.postgresql.org/documentation/changelog.html#version_42.2.2

You can download the PostgreSQL JDBC Driver at https://jdbc.postgresql.org/download.html

Categories: Informatika

Announcing the Release of BDR 1.0.5

2018, March 16 - 01:00

2ndQuadrant today announced the release of BDR 1.0.5. BDR is the first open source multi-master replication system for PostgreSQL to reach full production status. This release includes the updated PostgreSQL server version to support the Postgres-BDR 9.4.17 extension, containing all of the fixes from the PostgreSQL 9.4.17 release.

The fixes and improvements included in this release are:

  • Work around a core postgres reorderbuffer corruption bug with a change in the BDR output plugin.
  • Ignore column-count mismatches if the mismatched columns are all nullable or dropped. This makes recovery from some kinds of operator errors simpler, and with sufficient care can be used to bypass DDL locking for adding new nullable columns to tables.
  • Fix possible deadlock in the apply worker in the find_pkey_tuple() function
  • Stricter memory context handling and leak prevention during apply. In particular be careful not to fall back to TopMemoryContext. This may help some possible memory leak issues.
  • Reset the apply worker memory context on every commit, not just when all messages have been consumed. May help with some possible memory leak issues.
  • Skip BDR 1.0.4 and bump the version straight to 1.0.5 to match BDR2.

Download and installation instructions are available here.

2ndQuadrant (Developers of Postgres-BDR) provides support as well as consultation and training for Postgres-BDR. With deep knowledge of distributed databases in PostgreSQL, 2ndQuadrant will evaluate individual use cases and determine the most suitable product or solution.

Postgres-BDR is also available and supported by 2ndQuadrant in the Cloud.

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

Categories: Informatika

PostgreSQL 10.3, 9.6.8, 9.5.12, 9.4.17, and 9.3.22 released!

2018, March 1 - 01:00
2018-03-01 Security Update Release

The PostgreSQL Global Development Group has released an update to all supported versions of the PostgreSQL database system, including 10.3, 9.6.8, 9.5.12, 9.4.17, and 9.3.22.

The purpose of this release is to address CVE-2018-1058, which describes how a user can create like-named objects in different schemas that can change the behavior of other users' queries and cause unexpected or malicious behavior, also known as a "trojan-horse" attack. Most of this release centers around added documentation that describes the issue and how to take steps to mitigate the impact on PostgreSQL databases.

We strongly encourage all of our users to please visit A Guide to CVE-2018-1058: Protect Your Search Path for a detailed explanation of CVE-2018-1058 and how to protect your PostgreSQL installations.

After evaluating the documentation for CVE-2018-1058, a database administrator may need to take follow up steps on their PostgreSQL installations to ensure they are protected from exploitation.

Security Issues

One security vulnerability is addressed in this release:

  • CVE-2018-1058: Uncontrolled search path element in pg_dump and other client applications

Please visit A Guide to CVE-2018-1058: Protect Your Search Path for a full explanation of the CVE-2018-1058.

Bug Fixes and Improvements

This update fixes several bugs reported since the last cumulative update. Some of these issues affect only version 10, but many affect all supported versions. These fixes include:

  • Prevent logical replication from trying to replicate changes for unpublishable relations, such as materialized views and the "information_schema" tables
  • Fix for a common table expression (WITH clause) returning correct results when being referenced in a subplan where there are concurrent-update rechecks
  • Fix for an unexpected query planner error in certain cases where there are overlapping merge join clauses in an OUTER JOIN.
  • Fix for potential data corruption with materialized views after running pg_upgrade. If receiving errors such as "could not access status of transaction" or "found xmin from before relfrozenxid" on materialized views, please use "REFRESH MATERIALIZED VIEW" without "CONCURRENTLY" to fix.
  • Several fix for pg_dump, including a fix to help with the future work of cross-table statistics
  • Fix for reporting a PL/Python stack trace relative to inner PL/Python functions
  • Allow contrib/auto_explain to range up to INT_MAX, which is about 24 days
  • Mark assorted configuration variables as PGDLLIMPORT, to ease porting extension modules to Windows
Acknowledgements

The PostgreSQL Global Development Group would like to thank Arseniy Sharoglazov for reporting CVE-2018-1058 to the security team.

Links
Categories: Informatika

dbMigration .NET v7.6 released

2018, February 18 - 01:00

dbMigration .NET v7.6 is a simple, easy and intuitive multiple database migration and sync tool, With it you can easily migrate schema and data to PostgreSQL and vice versa without complicated procedures.

Free, All-In-One, Portable, Single executable file and Multi-language.

Major New features and improvements from version 6.6 to 7.6:

  • Startup, Data migration and Data synchronization performance improvements
  • Added Connection List
  • Added changing global table and column case
  • Added Sync settings: Skip New, Updated and Deleted Rows
  • Added Bulk Copy Mode for SQL Server/SQL Azure/IBM DB2/Informix and NuoDB
  • Improved Automatically generate foreign keys
  • Improved Migrating data with a SQL statement
  • Improved Data Synchronization
  • Improved Automatic Mapping Types
  • Improved Custom Mapping Types
  • Improved Command-Line
  • ...and more
The new version is immediately available for download.
Categories: Informatika

Announcing The Release Of repmgr 4.0.3

2018, February 15 - 01:00

Oxford, United Kingdom - February 15, 2018

2ndQuadrant announces the release of repmgr 4.0.3. repmgr is the most popular tool for PostgreSQL replication and failover management. It enhances and complements PostgreSQL's built-in replication capabilities, making 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 4.0.3 includes the following usability enhancements related to logging/diagnostics, event notifications, and pre-action checks:

  • Improve repmgr standby switchover behavior when pg_ctl is used to control the server and logging output is not explicitly redirected.
  • Improve repmgr standby switchover log messages and provide new exit code ERR_SWITCHOVER_INCOMPLETE when old primary could not be shut down cleanly.
  • Add check to verify the demotion candidate can make a replication connection to the promotion candidate before executing a switchover.
  • Add check for sufficient walsenders and replication slots on the promotion candidate before executing repmgr standby switchover.
  • Add --dry-run mode to repmgr standby follow.
  • Provide information about the primary node for repmgr standby register and repmgr standby follow event notifications.
  • Add standby_register_sync event notification, which is fired when repmgr standby register is run with the --wait-sync option and the new or updated standby node record has synchronized to the standby.
  • When running repmgr cluster show, if any node is unreachable, output the error message encountered in the list of warnings

This release contains the following bug fixes:

  • Ensure an inactive data directory can be overwritten when cloning a standby.
  • repmgr node status upstream node display fixed.
  • repmgr primary unregister clarify usage and fix --help output.
  • Parsing of pg_basebackup_options fixed.
  • Ensure the pg_subtrans directory is created when cloning a standby in Barman mode
  • repmgr witness register fix primary node check.

For a detailed list of all fixed bugs, please read the full release notes here.

We highly recommend upgrading to repmgr 4.0.3 at the earliest opportunity available. For this release, a simple package upgrade and restart of repmgrd (if running) is required.

Download is available here and installation instructions are available here.

repmgr is developed and maintained by 2ndQuadrant - your diligent team of PostgreSQL experts.

repmgr is distributed under GPL v3.

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

Categories: Informatika

Pgpool-II 3.7.2, 3.6.9, 3.5.13, 3.4.16 and 3.3.20 are now officially released.

2018, February 13 - 01: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:

  • 3.7.2
  • 3.6.9
  • 3.5.13
  • 3.4.16
  • 3.3.20

These are the latest stable minor versions of each major versions of Pgpool-II. 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

OmniDB 2.5 Released - Now with Support for Oracle Databases

2018, February 12 - 01:00

Oxford, United Kingdom — February 12, 2018

2ndQuadrant proudly announces the release of OmniDB 2.5. OmniDB is an interactive and powerful, yet lightweight, browser-based database management tool.

OmniDB 2.5 now allows users to manage multiple databases in a unified workspace with a user-friendly and fast-performing interface.

OmniDB 2.5 introduces the following features and improvements:

  • Basic support for Oracle databases. Users can manage, connect, and interact with Oracle databases using most of the same features provided to manage PostgreSQL databases.
  • New DDL Panel. A new panel located below the treeview displays properties and DDL of the currently selected node.

For a complete list of updates, read the OmniDB change tracker here.

OmniDB 2.5 is available for download here and installation instructions are available here.

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

About 2ndQuadrant

2ndQuadrant is your diligent team of PostgreSQL experts. As the largest collective organization of PostgreSQL contributors, we provide customers with more than just expertise - we give peace of mind. We apply knowledge from over 100 years of combined code contributions to the PostgreSQL project with more than 16 years of hands-on experience through customer engagements to deliver high-quality, customized services - making 2ndQuadrant the Gold Standard for PostgreSQL products & services. Our focus on service quality is reflected in the consistent best-in-class NPS score of over 75 for more than 2 years. Spanning 22 countries and 5 continents, we sustain a local presence to better serve our customers.

Categories: Informatika

PostgreSQL 10.2, 9.6.7, 9.5.11, 9.4.16, and 9.3.21 released!

2018, February 8 - 01:00

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 10.2, 9.6.7, 9.5.11, 9.4.16, 9.3.21. This release fixes two security issues. This release also fixes issues with VACUUM, GIN indexes, and hash indexes that could lead to data corruption, as well as fixes for using parallel queries and logical replication.

All users using the affected versions of PostgreSQL should update as soon as possible. Please see the notes on "Updating" below for any post-update steps that may be required.

Please note that PostgreSQL changed its versioning scheme with the release of version 10.0, so updating to version 10.2 from 10.0 or 10.1 is considered a minor update.

Security Issues

Two security vulnerabilities have been fixed by this release:

  • CVE-2018-1052: Fix the processing of partition keys containing multiple expressions
  • CVE-2018-1053: Ensure that all temporary files made with "pg_upgrade" are non-world-readable
Bug Fixes and Improvements

This update fixes over 60 bugs reported in the last few months. Some of these issues affect only version 10, but many affect all supported versions:

  • Fix crash and potential disclosure of backend memory when processing partition keys containing multiple expressions
  • Fix potential disclosure of temporary files containing database passwords created by pg_upgrade by not allowing these files to be world-accessible
  • Fix cases where VACUUM would not remove dead rows if they were updated while "key-share" locked, leading to potential data corruption
  • Fix for GIN indexes to prevent bloat by ensuring the pending-insertions list is cleaned up by VACUUM
  • Fix potential index corruption with hash indexes due to failure to mark metapages as dirty
  • Fix several potential crash scenarios for parallel queries, including when a bitmap heap scan cannot allocate memory
  • Fix several potential hang-ups in parallel queries, including when a parallel worker fails to start
  • Fix collection of EXPLAIN statistics from parallel workers
  • Prevent fake deadlock failures when multiple sessions are running CREATE INDEX CONCURRENTLY
  • Fix for trigger behavior when using logical replication
  • Several fixes for "walsender" functionality to improve stability as well as visibility into the replication process
  • Fix logical decoding to correctly clean up disk files for crashed transactions
  • Several fixes for identity columns, including disallowing identity columns on tables derived from composite types and partitions
  • Fix handling of list partitioning constraints for partition keys of boolean and array types
  • Fix incorrectly generated plans for UPDATE and DELETE queries when a table has a mix of inherited regular and foreign child tables
  • Fix incorrect query results from cases involving GROUPING SETS when used with flattened subqueries
  • Fix UNION/INTERSECT/EXCEPT over zero columns, e.g. "SELECT UNION SELECT;"
  • Several fixes for subqueries within a LATERAL subquery
  • Several improvements for query planning estimation
  • Allow a client that supports SCRAM channel binding, such as a future version of PostgreSQL or libpq, to connect to a PostgreSQL 10 server
  • Fix sample INSTR() functions used to help transition from Oracle(r) PL/SQL to PostgreSQL PL/pgSQL to correctly match Oracle functional behavior
  • Fix pg_dump to make permissions (ACL), security label, and comment entries reliably identifiable in archive outputs
  • Modify behavior for contrib/cube's "cube ~> int" operator to make it compatible with KNN search. This is a backwards incompatible change and any expression indexes or materialized views using this operator will need to be reindexed and refreshed, respectively.
  • Several fixes in contrib/postgres_fdw to prevent query planner errors
  • Added modern examples of auto-start scripts for PostgreSQL on macOS in the contrib/start-scripts/macos directory
  • Several fixes for Windows, including postmaster startup and compatibility with libperl
  • Spinlock fixes and support for Motorola 68K and 88K architectures

This update also contains tzdata release 2018c, with updates for DST law changes in Brazil, Sao Tome and Principe, plus historical corrections for Bolivia, Japan, and South Sudan. The US/Pacific-New zone has been removed (it was only an alias for "America/Los_Angeles" anyway).

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.

If your installation is affected by one of the following issues, you may need to perform additional post-update steps:

  • Users affected by the GIN and hash index issues should consider rebuilding these indexes
  • Users who copied the "INSTR" example from the PostgreSQL documentation should analyze their code to determine if they need to apply the corrected "INSTR" example
  • Users who use the "~>" operator found in "contrib/cube" with expression indexes or materialized views will need to reindex and refresh them, respectively. This change is also backwards incompatible, so please test any code using this operator before releasing to a production environment.

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.

Links
Categories: Informatika

Citus 7.2: CTEs, complex subqueries, set operations, and more

2018, January 26 - 01:00

The Citus 7.2 extension to Postgres now includes expanded support for distributed SQL, the distribution of complex subqueries across multiple nodes, easier partition management through integration with pg_partman, and more. Developers building real-time analytics dashboards and multi-tenant applications will benefit the most.

You can find more information in the Citus 7.2 release notes.

Citus 7.2 is compatible with PostgreSQL 9.6 and 10. You can try Citus 7.2 by following the download instructions or one-click deploy through the Citus Cloud console.

Categories: Informatika

PostgreSQL JDBC 42.2.1 released

2018, January 25 - 01:00

The PostgreSQL JDBC team is pleased to announce the release of version 42.2.1. This is primarily to fix some regressions:

Most notably:

  • Avoid connection failure when DateStyle is set to ISO (~PgBouncer)
  • Package scram:client classes, so SCRAM works when using a shaded jar
  • reWriteBatchedInserts=true causes syntax error with ON CONFLICT Issue
  • Avoid failure in getPGArrayType when stringType=unspecified
Categories: Informatika

Pages

Theme by me