Neues vom PostgreSQL Planet
Read our interview with Fabrice Vaillant who will talk about going From a Legacy Relational DB to an Event Queue.
Every year, on the second Wednesday of November, Esri (“the Microsoft of GIS”) promotes a day of celebration, “GIS Day” in which the members of our community unite to tell the world about the wonders of cartography and spatial data and incidentally use their software a lot in the process.
Read our interview with Daniel Vérité who will talk about Staying Safe from ACID Rains.
Version 4.0 of Pgpool-II added some very exciting security and authentication features to make it more relevant and useful for enterprise environments. It adds support for providing encrypted passwords in pool_passwd and configuration files and lets the administrators chose different authentication methods to be used for the Client<–>Pgpool-II and Pgpool-II<–>PostgreSQL authentications.
Last time we imported OpenStreetMap datasets from Iceland to PostGIS.
To quickly visualize our results, we will now use QGIS to render our datasets and generate some nice maps on the client.
Let’s start with our prerequisites:
Read our interview with Christophe Pettus who will talk about Database Disasters and How to Find Them.
A very non-scientific comparison about the two database engines.
The lock is an essential part of a database system. In PostgreSQL, there are various locks, such as table lock, row lock, page lock, transaction lock, advisory lock, etc. Some of these locks are automatically added to complete the database functions during the operation of the database system, and some are manually added for the elements in PostgreSQL through some SQL commands. This blog explores the locks in PostgreSQL.
PostgreSQL Conference Germany 2020 in Stuttgart, Germany, on May 15th is now open for registrations.
The Call for Papers is already closed, and we are working with the last speakers to confirm their talks, and we will have a full schedule published soon.
There are still a few "EARLYBIRD" tickets available, until end of February.
See you in Stuttgart!
If you are using Azure PostgreSQL and have upgraded your client side libpq to version 12 (which can happen automatically for example if you use the PostgreSQL apt repositories), you may see connection attempts fail with symptoms like:
The PostGIS Team is pleased to release PostGIS 3.0.1.
Best served with PostgreSQL 12.2, GEOS 3.8.0, SFCGAL 1.3.7, GDAL 3.0.4, PROJ 6.3.1, protobuf-c 1.3.3, json-c 0.13.1.Continue Reading by clicking title hyperlink ..
PG9.6 has added Parallel execution of sequential scans, joins, and aggregates.
The PostgreSQL caching system has always been a bit of a miracle to many people and many have asked me during consulting or training sessions: How can I figure out what the PostgreSQL I/O cache really contains? What is in shared buffers and how can one figure out? This post will answer this kind of question and we will dive into the PostgreSQL cache.
Creating a simple sample database
Before we can inspect shared buffers we have to create a little database. Without data the stuff we are going to do is not too useful: