Monday, January 22

Tag: postgres

Webinar: Introduction to JSON data types in PostgreSQL [Follow Up]

Liaqat's PlanetPostgreSQL, Webinars
On 12-Dec-2017, 2ndQuadrant held the first in a series of PostgreSQL webinars. The session was conducted by Andrew Dunstan, Principal Contributor of JSON functionality to PostgreSQL and Senior Developer & PostgreSQL Committer at 2ndQuadrant. As promised, the recording of the Webinar is now available. Those who couldn't make it to the live session, can now view Introduction to JSON data types in PostgreSQL here. While Andrew was able to address many questions live, there were several queries that couldn’t be answered due to time restrictions. Andrew Dunstan has taken time to answer those questions below. Q1: Since PostgreSQL 9.4 JSONB supports GIN index, does that means that GIN index has a better performance on JSONB? What about JSON? A:  There is no direct indexing (more…)

Using the PostgreSQL TAP framework in extensions

Craig's PlanetPostgreSQL
Support for using the TAP protocol to run extended regression tests was added to PostgreSQL back in 9.4 with the adoption of Perl's prove tool and Test::More to test initdb, pg_basebackup, etc. Since then the TAP-based tests have been greatly expanded, particularly with the advent of the src/test/recovery tests and the PostgresNode module in PostgreSQL 9.6. PostgreSQL now comes with a built-in test harness for easily starting up postgres instances, creating and restoring backups for replication, setting up streaming, and lots more. You can now use this to test your extensions. pg_regress and its limitations Extensions have long supported pg_regress based tests. Just drop the test scripts in sql/. Put the expected results in expected/. List the test names (sans directory and file (more…)

Barman 2.1 and the new –archive option

Giulio's PlanetPostgreSQL
Barman 2.1 Version 2.1 of Barman, backup and recovery manager for PostgreSQL, was released Thursday, Jan. 5. The new release, along with several bugfixes, introduces preliminary support for the upcoming PostgreSQL 10, and adds the --archive option to the switch-xlog command. switch-xlog --archive The new --archive option is especially useful when setting up a new server. Until now, the switch-xlog command used to force the PostgreSQL server to switch to a different transaction log file. Now, Barman also gives the --archive option, which triggers WAL archiving after the xlog switch, and forces Barman to wait for the archival of the closed WAL file. By default Barman expects to receive the WAL in 30 seconds, the amount of seconds to wait can be changed using the --archive-timeout (more…)
PGDay.IT 2016 in Prato, Italy

PGDay.IT 2016 in Prato, Italy

2ndQuadrant, Jonathan's PlanetPostgreSQL
This year, the ITPUG (Italian Postgres User Group) organized PGDay in Prato, my hometown and city where the association was born, although most of the members are from outside of the Tuscany region. It was my pleasure to contribute to the community by sharing my professional experience. I gave a talk about PostgreSQL on Network File System, a research based on crash tests to prove reliability using PostgreSQL on NFS. Sharing my PostgreSQL experience with the participants was useful and pleasant. During the event, I had the chance to attend the talk about tools for upgrading Postgres between major releases given by Denis Gasparin; and the one about ULSS's (Regional Healthcare System) migration to Open Source, given by Giorgio Roncolato, proving that more institutions than we thought (more…)

The PostgreSQL License – What Does It Mean For My Business?

Umair's PlanetPostgreSQL
When I talk to various people about PostgreSQL, based on where they are in the process of analyzing it, I get asked many similar questions. One of the most frequently asked questions is: What is the PostgreSQL licensing model? Here is my attempt to address this question from the perspective of what the PostgreSQL license means for your business. Go Ahead, Read It - It’s Really Not That Scary Let’s be honest with ourselves, we are really not in the habit of reading license agreements - they are best left to the legal department to decipher. And seriously, licenses have become so complex and so detailed that even if I try really really hard to read just a few clauses, my head starts to hurt. The PostgreSQL License is different though. I have reproduced the license in full at (more…)