PostreSQL.org

PostgreSQL 11 Beta 4 Released

The PostgreSQL Global Development Group announces that the fourth beta release of PostgreSQL 11 is now available for download. This release contains previews of all features that will be available in the final release of PostgreSQL 11 (though some details could change before a release candidate is made available) as well as bug fixes that were reported during the third beta.

This is likely the last beta release for PostgreSQL 11 before a release candidate is made available.

In the spirit of the open source PostgreSQL community, we strongly encourage you to test the new features of PostgreSQL 11 in your database systems to help us eliminate any bugs or other issues that may exist.

Upgrading to PostgreSQL 11 Beta 4

To upgrade to PostgreSQL 11 Beta 4 from Beta 3 or an earlier version of PostgreSQL 11, you will need to use a strategy similar to upgrading between major versions of PostgreSQL (e.g. pg_upgrade or pg_dump / pg_restore). For more information, please visit the documentation section on upgrading.

Changes Since 11 Beta 3

There have been many bug fixes for PostgreSQL 11 reported during the Beta 3 period and applied to the Beta 4 release. This release also includes other bug fixes that were reported for supported versions of PostgreSQL that also affected PostgreSQL 11. These fixes include:

• JIT compilation is disabled by default. To enable JIT compilation, you must set jit = on in your configuration file or in a session
• Enforce that names for constraints are unique
• Several fixes for stored procedures, including improved hints and documentation around usage
• Several fixes for partitioning, including fixes for runtime partition pruning
• Fix for parallelized CREATE INDEX by disallowing builds on mapped catalog relations
• Fix for REINDEX to prevent unprivileged users from reindexing shared catalogs in certain cases
• Memory-leak fix when multiple calls are made to XMLTABLE in a single query
• Several fixes for pg_verify_checksums
• Several fixes for libpq, including a fix to only look up a hostname when explicitly requested to do so
• Several pg_upgrade fixes, including handling event triggers in extensions correctly
• Several fixes for pg_dump and pg_restore

For a detailed list of fixes, please visit the open items page.

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 release of PostgreSQL 11. 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 fourth beta release of PostgreSQL 11. In all likelihood, this is the final beta release of PostgreSQL 11 before one or more release candidates are made available. For further information please see the Beta Testing page.

Links

• Download
• Beta Testing Information
• PostgreSQL 11 Beta Release Notes
• PostgreSQL 11 Open Issues
• Submit a Bug

The PostgreSQL Core team are pleased to announce that following a long consultation process, the project’s Code of Conduct (CoC) has now been finalised and published here.

Please take time to read and understand the CoC, which is intended to ensure that PostgreSQL remains an open and enjoyable project for anyone to join and participate in.

A Code of Conduct Committee has been formed to handle any complaints. This consists of the following volunteers:

• Stacey Haysler (Chair)
• Lætitia Avrot
• Vik Fearing
• Jonathan Katz
• Ilya Kosmodemiansky

We would like to extend our thanks and gratitude to Stacey Haysler for her patience and expertise in helping develop the Code of Conduct, forming the committee and guiding the work to completion.

2ndQuadrant announced today the release of Postgres-XL 10r1beta1, now available for download here.

Postgres-XL is a massively parallel database built on top of - and very closely compatible with - community PostgreSQL and its set of advanced features. It supports both Business Intelligence workloads and high-volume transactional write and read workloads, all on the same platform.

Postgres-XL is fully open source; as we begin to move towards a fully parallel, sharded version of core PostgreSQL, many parts of Postgres-XL will feed directly or indirectly into later releases of PostgreSQL.

Postgres-XL 10R1Beta1 introduces the following enhancements from major PostgreSQL latest releases:

PostgreSQL 10

• Declarative table partitioning
• Improved query parallelism
• Significant general performance improvements
• Improved monitoring and control

PostgreSQL 9.6

• Parallel execution of sequential scans, joins and aggregates
• Avoid scanning pages unnecessarily during vacuum freeze operations
• Substantial performance improvements, especially in the area of scalability on multi-CPU-socket servers
• Full-text search can now search for phrases (multiple adjacent words)

This new release also includes several bug fixes and Postgres-XL specific enhancements. The distributed planner code has been rewritten to utilise advances in the PostgreSQL code.

For a complete list of updates and bug fixes, read full release notes here.

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

PostgreSQL Conference Europe is pleased to announce that the schedule for its 2018 event, to be held in Lisbon, Portugal, from 23rd - 26th October, has now been published.

The schedule is, of course, subject to changes.

This year, Paul Ramsey will present the opening keynote, on the topic of the past, present, and future for spatial data in PostgreSQL. Paul is a founder of the PostGIS project and a long-time PostgreSQL community contributor.

PostgreSQL Conference Europe 2018 is the 10th annual PostgreSQL Conference Europe, previous events having been held in cities such as Warsaw, Tallinn, Vienna, Madrid, Dublin, Prague, and Amsterdam, attracting hundreds of PostgreSQL users and developers.

Tickets are available here, subject to availability. With a history of the event selling out, we encourage everybody who wants to attend to register as soon as possible to guarantee a seat.

We still have seats left at some of the training sessions held the day before the main conference, taught by PostgreSQL experts from around the world. Tickets for training sessions are subject to availability here.

We look forward to seeing you in Lisbon!

Oxford, United Kingdom - September 5, 2018

2ndQuadrant today announced the release of repmgr 4.1.1

repmgr is the most popular tool for PostgreSQL replication and failover management. It enhances and complements the built-in replication capabilities in PostgreSQL; 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.

Packages are available via public RPM and APT repositories from 2ndQuadrant. Installation packages documentation is available here.

repmgr 4.1.1 presents the following usability enhancements:

• repmgr standby switchover --dry-run no longer copies external configuration files to test if they can be copied; this avoids making any changes to the target system.
• repmgr cluster cleanup now includes cluster_cleanup event.
• repmgr standby switchover improves detection of free walsenders.
• Improved messages emitted during repmgr standby promote.

This release presents important enhancements to repmgrd, such as:

• Always reopens the log file after receiving SIGHUP, previously this happened only when a configuration file change was detected.
• Reports version number after logger initialisation.
• Improved cascaded standby failover handling.
• Improved reconnection handling after brief network outages - if monitoring data is being collected, this could lead to orphaned sessions on the primary.
• Check promote_command and follow_command are defined when reloading configuration. These were checked on startup but not reloaded by repmgrd, making it possible to build repmgrd with invalid values.

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

We recommend upgrading to this version as soon as possible. This release can be installed as a simple package upgrade from repmgr 4.x.

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

A potential security issue (CVE-2018-10936) has been addressed. It was theoretically possible to provide an SSL Factory and not check the host name if a host name verifier was not provided to the driver. During the process of investigating this a number of changes have been made.

ssl=true now means verify-full. This is a diversion from libpq which defaults to no validation or verification. With ssl=true or verify-full the driver will verify the ssl certificate and validate that the host is the host named in the certificate.

The driver now also supports allow and prefer, see https://jdbc.postgresql.org/documentation/head/ssl-client.html for details.

Full Convert allows easy copying of tables and data between 40 or so supported databases. It will create all the tables, copy all of your data, then create indexes and foreign keys. It has powerful mapping and customization features and uses optimal copying mode for each table separately to achieve the best possible throughput.

Import into PostgreSQL from any of the source databases has been highly optimized, while keeping memory consumption extremely low. Typical conversion from almost any source database into local PostgreSQL target is in low hundreds of thousands of records per second with under 200MB of RAM usage. We support almost all Postgres data types, including spatial types.

Recent updates:

• Fixed certain edge cases in Paradox BCD data reading
• Updated support for Java databases (Derby, H2, HSQLDB)
• Fixed Informix boolean datatype detection
• Fixed reading of MySQL data types from SQL script files
• Added missing IKVM dlls
• Fixed HSQLDB reserved word handling
• Improved auto-detection of Paradox and Interbase databases
• Added support for SIARD 2.1
• Added int datatype to SQLite target instead of forcing bigint for all integral types
• Added support for Amazon RedShift
• Fixed handling of certain Access driver expections

For more information, please visit the product page: Full Convert.

We are down to counting the days until PostgresOpen SV 2018 in downtown San Francisco, September 5th to 7th! Registration is closing in coming days so make sure to grab your tickets while you still can. We also still have a few seats in our tutorials open, so if you're hoping to attend a half day tutorial/training save your seat today.

You can check out the schedule of tutorials and talks here

Then grab your tickets

If you still need a room for the conference you can reserve while available

Special thanks to our sponsors! Be sure to check them out as we've just added on our second Diamond sponsor, and thanks to all of our other level sponsors as well.

This year we are pleased to be able to recognize our Diamond sponsors:

CitusData

Microsoft

Be sure to check out our site to see all of our Gold, Silver and Supporter sponsors, and our Community Partners here

Sponsorship opportunities are still available! Please review our prospectus.

PostgresOpen wouldn't be able to happen without the tireless efforts of the individuals at the United States PostgreSQL Association (PgUS), please consider joining! PgUS is the non-profit organization which backs PostgresOpen and other events.

We look forward to seeing everyone in San Francisco in of weeks!

PremiumSoft CyberTech Ltd. today announced an upgraded version of Navicat for PostgreSQL - Version 12.1.

Navicat for PostgreSQL is an easy-to-use graphical tool for PostgreSQL database development. From writing simple SQL queries to developing complex databases, Navicat for PostgreSQL is designed to accommodate a wide range of users, from PostgreSQL beginners to seasoned developers. Connect to local/remote PostgreSQL servers and compatible with cloud databases like Amazon Redshift, Amazon Aurora, Amazon RDS, Google Cloud, Microsoft Azure, Alibaba Cloud and Huawei Cloud, and all PostgreSQL database objects.

New key features in Navicat for PostgreSQL version 12 includes:

• Support Partitioned Table for PostgreSQL 10
• Brand new Filter Wizard
• UI and UX Improvement
• Cross-platform is available

For detail, please visit: https://www.navicat.com/en/products/navicat-for-postgresql

Plans, Pricing and Availability

Navicat for PostgreSQL which supports multiple database server type connection is now priced starting from US$119. For detailed pricing on Navicat, please visit: https://www.navicat.com/en/store/navicat-for-postgresql

About Navicat Navicat is the choice of over 3 million database users all around the world. Over 150,000 registered customers across 7 continents and 138 countries have chosen our products.

About PremiumSoft PremiumSoft CyberTech Ltd. is a multinational corporation headquartered in Hong Kong, the company was founded in 1999 and has developed numerous award-winning products over the years.

PgBouncer 1.9.0 is out. It contains several new features to facilitate and monitor controlled switchover in high-availability architectures. There are also a number of documentation improvements and fixes. See

https://pgbouncer.github.io/2018/08/pgbouncer-1-9-0

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

PgBouncer is a lightweight connection pooler for PostgreSQL.

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 10.5, 9.6.10, 9.5.14, 9.4.19, 9.3.24. This release fixes two security issues as well as bugs reported over the last three months.

If you have untrusted users accessing your system and you are either running PostgreSQL 9.5 or a newer version OR have installed the dblink or postgres_fdw extensions, you must apply this update as soon as possible. All other users can upgrade at the next convenient downtime.

Please note that PostgreSQL changed its versioning scheme with the release of version 10.0, so updating to version 10.5 from any 10.x release is considered a minor update.

The PostgreSQL Global Development Group also announces that the third beta release of PostgreSQL 11 is now available for download. This release contains previews of all features that will be available in the final release of PostgreSQL 11 (though some details of the release could change before then) as well as bug fixes that were reported during the second beta.

Security Issues

Two security vulnerabilities have been closed by this release:

CVE-2018-10915: Certain host connection parameters defeat client-side security defenses

libpq, the client connection API for PostgreSQL that is also used by other connection libraries, had an internal issue where it did not reset all of its connection state variables when attempting to reconnect. In particular, the state variable that determined whether or not a password is needed for a connection would not be reset, which could allow users of features requiring libpq, such as the dblink or postgres_fdw extensions, to login to servers they should not be able to access.

You can check if your database has either extension installed by running the following from your PostgreSQL shell:

\dx dblink|postgres_fdw

Users are advised to upgrade their libpq installations as soon as possible.

The PostgreSQL Global Development Group thanks Andrew Krasichkov for reporting this problem.

CVE-2018-10925: Memory disclosure and missing authorization in INSERT ... ON CONFLICT DO UPDATE

An attacker able to issue CREATE TABLE can read arbitrary bytes of server memory using an upsert (INSERT ... ON CONFLICT DO UPDATE) query. By default, any user can exploit that. A user that has specific INSERT privileges and an UPDATE privilege on at least one column in a given table can also update other columns using a view and an upsert query.

Bug Fixes and Improvements

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

These fixes include:

• Several fixes related to VACUUM, including an issue that could lead to data corruption in certain system catalog tables
• Several fixes for replaying write-ahead logs, including a case where a just-promoted standby server would not restart if it crashed before its first post-recovery checkpoint
• Several performance improvements for replaying write-ahead logs
• Several fixes for logical replication and logical decoding, including ensuring logical WAL senders are reporting the streaming state correctly
• Allow replication slots to be dropped in single-user mode
• Fix to have variance and similar aggregate functions return accurate results when executed using parallel query
• Fix SQL-standard FETCH FIRST syntax to allow parameters ($n), as the standard expects
• Fix to ensure that a process doing a parallel index scan will respond to signals, such as one to abort a query
• Fix EXPLAIN's accounting for resource usage, particularly buffer accesses, in parallel workers
• Several fixes for the query planner including improving the cost estimates for hash-joins and choosing to use indexes for mergejoins on composite type columns
• Fix performance regression related to POSIX semaphores for multi-CPU systems running Linux or FreeBSD
• Fix for GIN indexes that could lead to an assertion failure after a pg_upgrade from a version before PostgreSQL 9.4
• Fix for SHOW ALL to display superuser configuration settings to roles that are allowed to read all settings
• Fix issue where COPY FROM .. WITH HEADER would drop a line after every 4,294,967,296 lines processed
• Several fixes for XML support, including using the document node as the context for XPath queries as defined in the SQL standard, which affects the xpath and xpath_exists functions, as well as XMLTABLE
• Fix libpq for certain cases where hostaddr is used
• Several ecpg fixes for Windows
• Fix password prompting in Windows client programs so that echo is properly disabled
• Several pg_dump fixes, including correctly outputting REPLICA IDENTITY properties for constraint indexes
• Make pg_upgrade check that the old server was shut down cleanly

This update also contains tzdata release 2018e, with updates for North Korea. The 2018e also reintroduces the negative-DST changes that were originally introduced in 2018a, which affects historical and present timestamps for Ireland (1971-), as well as historical timestamps for Namibia (1994-2017) and the former Czechoslovakia (1946-1947). If your application is storing timestamps with those timezones in the affected date ranges, we ask that you please test to ensure your applications behave as expected.

PostgreSQL 11 Beta 3 Fixes and Improvements

PostgreSQL 11 Beta 3 contains applicable bug fixes from the cumulative release as well as over 20 fixes of its own. For a full list of fixes for PostgreSQL 11 Beta 3, please visit the open items page.

EOL Warning for PostgreSQL 9.3

PostgreSQL 9.3 will become end-of-life after the next planned release in November. We urge users to start planning an upgrade to a later version of PostgreSQL as soon as possible. See our Versioning Policy for more information

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.

Upgrading to PostgreSQL 11 Beta 3

To upgrade to PostgreSQL 11 Beta 3 from Beta 1 or 2, or a earlier version of PostgreSQL, you will to use a strategy similar to upgrading between major versions of PostgreSQL (e.g. pg_upgrade or pg_dump / pg_restore). For more information, please visit the documentation section on upgrading.

PostgreSQL 11 Beta Schedule and Testing

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

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 release of PostgreSQL 11. We greatly appreciate all of the testing performed to date as we get closer to the final release. Your feedback and testing will help determine the final tweaks on the new features, so please continue to test. The quality of user testing helps determine when we can make a final release.

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

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

Links

• Download
• Release Notes
• PostgreSQL 11 Beta Release Notes
• Security Page
• Beta Testing Information
• PostgreSQL 11 Open Items
• Versioning Policy
• Follow @postgresql on Twitter

PostgresOpen SV 2018 Schedule Released

We are down to counting the days until PostgresOpen SV 2018, the US PostgreSQL Community Conference, in downtown San Francisco, September 5th to 7th!

Our exciting schedule has been released, which you can go to now here.

There's only a couple of weeks left to take advantage of our discounted hotel rate at the wonderful Parc 55 in downtown San Francisco! Get your hotel room booked now here.

Our trainings and sponsored workshops are starting to fill up, be sure to register for the conference and the training sessions you're interested in and get your tickets here.

Special thanks to our sponsors! Be sure to check them out as we've just added on our second Diamond sponsor, and thanks to all of our other level sponsors as well.

This year we are pleased to be able to recognize our Diamond sponsors:

CitusData

Microsoft

Be sure to check out our site to see all of our Gold, Silver and Supporter sponsors, and our Community Partners here.

Sponsorship opportunities are still available! Please visit our becoming a sponsor page here. to review our prospectus and contact us at program2018@postgresopen.org.

PostgresOpen wouldn't be able to happen without the tireless efforts of the individuals at the United States PostgreSQL Association (PgUS), please consider joining! PgUS is the US-based recognized community non-profit organization which backs PostgresOpen, many meetups, and other events. Visit PgUS here.

We look forward to seeing everyone in San Francisco in less than a month!

Any questions? Please contact: program2018@postgresopen.org.

Stephen Frost & Craig Kerstiens PostgresOpen SV 2018 Committee Co-Chairs https://2018.postgresopen.org

dbMigration .NET v9.1 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 7.7 to 9.1:

• 50%+ performance improvement in the Transaction mode
• Startup, Disconnection performance improvements
• Added support for Partitioned tables in PostgreSQL 10+
• Added support for Foreign tables in PostgreSQL 9+
• Added support for macaddr8 datatype in PostgreSQL 10+
• Added Auto-generating CHECK constraints of tables
• Added Auto-generating DEFAULT values of columns
• Added Mapping column names from the target table
• Added Migrating TRIGGER definitions
• Added an option to change the global case of target objects as database default
• Added SQL Syntax Highlighting
• Added Displaying a progress indicator in a taskbar button
• Added Showing TABLE/VIEW types in tooltip
• Added Bulk Copy Mode for Oracle
• Improved Connection List
• Improved Automatic Mapping Types
• Improved Custom Mapping Types
• Improved Command-Line
• ...and more

The new version is immediately available for download.

Oxford, United Kingdom - July 31, 2018

2ndQuadrant today announced the release of repmgr 4.1.

repmgr is the most popular tool for PostgreSQL replication and failover management. It enhances and complements the built-in replication capabilities in PostgreSQL, 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.

Packages are available via public RPM and APT repositories from 2ndQuadrant. Installation packages documentation is available here.

This release introduces the following configuration file changes:

• Default for log_level is now INFO producing additional informative log output, without creating excessive additional log file volume, and matches the setting assumed for examples in the documentation.
• recovery_ min_ apply_delay now accepts a minimum value of zero

repmgr 4.1 presents important usability enhancements, such as:

• Always exit with an error if an unrecognized command line option is provided. This matches the behaviour of other PostgreSQL utilities such as psql.
• Add -q/--quiet option to suppress non-error output.
• repmgr cluster show, repmgr node check and repmgr node status return non-zero exit code if a node status issues is detected.
• Add --csv output option for repmgr cluster event.
• repmgr witness unregister can be run on any node, by providing the ID of the witness node with --node-id.
• repmgr standby switchover will refuse to run if an exclusive backup is taking place on the current primary.

For a detailed list of all repmgrd changes, enhancements, and bug fixes, please read the complete release notes here.

We recommend upgrading to this version as soon as possible. This release can be installed as a simple package upgrade from repmgr 4.x.

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

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.5
• 3.6.12
• 3.5.16
• 3.4.19
• 3.3.22

Please note that 3.3.22 is the last release of 3.3 series because 5 years has passed since 3.3 was out (2013/07/30).

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.

Intelligent Converters released Oracle-PostgreSQL Sync, a program for bi-directional incremental synchronization of Oracle and PostgreSQL databases.

For more information, please visit the product page: https://www.convert-in.com/o2psync.htm

This is primarily a fix for a regression related to fn timestampadd(SQL_TSI_MINUTE) SQL_TSI_MINUTE seems to be acting like SQL_TSI_SECOND in 42.2.3. PR 1250

See full changelog here

The JDBC project is proud to announce the latest version 42.2.3. This release fixes some annoyances such as:

• Reduce the severity of the error log messages when an exception is re-thrown. The error will be thrown to caller to be dealt with so no need to log at this verbosity by pgjdbc
• Support parenthesis in {oj ...} JDBC escape syntax
• getString for PGObject-based types returned "null" string instead of null
• Field metadata cache can be disabled via databaseMetadataCacheFields=0
• Properly encode special symbols in passwords in BaseDataSource
• Adjust date, hour, minute, second when rounding nanosecond part of a timestamp
• Encode URL parameters in BaseDataSource

As well as some performance enhancements:

• reduce memory allocations in query cache
• reduce memory allocations in SQL parser

The complete changelog can be reviewed here https://jdbc.postgresql.org/documentation/changelog.html#version_42.2.3

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

The JDBC team would like to thank everyone who contributed code and reviews: contributors

Oxford, United Kingdom — July 10, 2018

2ndQuadrant today released the new update to PGInstaller.

PGInstaller now includes support for the most popular spatial objects extension, PostGIS. It is available for PostgreSQL versions 9.5, 9.6 & 10.

PGInstaller provides a standalone, user-friendly installation for PostgreSQL based on a GUI for Windows, OSX and Linux. List of all supported platforms is available here.

PostGIS is a spatial database extension for PostgreSQL databases, adding support for geographic objects, allowing location queries to be run in SQL. It also adds functions, operators, and index enhancements that apply to these spatial types.

These additional functions, operators, index bindings and types augment the power of the core PostgreSQL DBMS; making it a fast, feature-rich, and robust spatial database management system.

PGInstaller is available for download here.

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

We are very glad to announce the 2.3.0 version of E-Maj.

E-Maj is a PostgreSQL extension which enables fine-grained write logging and time travel on subsets of the database.

This new version supports from 9.2 to v11 PostgreSQL versions. It is a new step in giving more flexibility in tables groups management. In particular, it allows to add tables or sequences to groups or move tables or sequences from one group to another without being obliged to stop/restart the logging mecanism (and loose the capability to 'rollback' to a previous point in time).

Both web clients, Emaj_web and the phpPgAdmin plugin, have been enhanced to take benefit from this feature.

Two new characters mode clients have been added. Written in perl, they bring the same features as the existing php clients: launch parallel E-Maj rollback and monitor E-Maj rollbacks.

The full documentation is available on line. The core extension is available at pgxn.org or github.org.

The phpPgAdmin plugin and the Emaj_web application are also available at github.org.

Have fun with E-Maj !