Neues vom PostgreSQL Planet

Neues vom PostgreSQL Planet Feed abonnieren
Planet PostgreSQL
Aktualisiert: vor 28 Minuten 3 Sekunden

Pavel Stehule: watch mode for pspg

27. Oktober 2019 - 8:25
I released version 2.5.0 of pspg.

Jonathan Katz: Monitoring PostgreSQL Clusters in Kubernetes

26. Oktober 2019 - 15:56

The open source PostgreSQL Operator provides many features that are required to run a production database-as-a-service on Kubernetes, including provisioning PostgreSQL clusters, performing backup and restore operations, and manag

cary huang: Vancouver Postgres Group Meetup Event – Kubernetes Best Practices for Distributed SQL databases

26. Oktober 2019 - 2:32

Date: October 24, 2019

Guest Speaker: Andrew Nelson, Developer Advocate from YugaByte

About Vancouver Postgres User Meetup Group

Vancouver Postgres is a Postgres user meetup group based in Vancouver, Canada. It specializes in building Postgres users to the related ecosystem including but not limited to technologies such as RDS Postgres, Aurora for Postgres, Google Postgres, PostgreSQL.Org Postgres, Greenplum, Timescale and ZomboDB.

Luca Ferrari: pgenv: adjust your PATH!

25. Oktober 2019 - 2:00

A few days ago we added the option to suggest you changes to your PATH to prevent version clashes.

pgenv: adjust your PATH!

In the following you can find another quick video that demonstrate how easy it is to get, almost automtically, a PostgreSQL 12 instance up and running on your local machine using pgenv.

Regina Obe: PostgreSQL 12 64-bit for Windows FDWs

24. Oktober 2019 - 1:55

We are pleased to provide binaries for file_textarray_fdw and odbc_fdw for PostgreSQL 12 Windows 64-bit.

To use these, copy the files into your PostgreSQL 12 Windows 64-bit install folders in same named folders and then run CREATE EXTENSION as usual in the databases of your choice. More details in the packaged README.txt

Avinash Kumar: Seamless Application Failover using libpq Features in PostgreSQL

23. Oktober 2019 - 18:58

When you build replication in PostgreSQL using Streaming replication, you cannot perform writes to a standby node; only reads. This way, you could offload reads or reporting queries to standby servers and send writes to master. Additionally, starting from PostgreSQL 10,

Michael Banck: pg_checksums 1.0 released

23. Oktober 2019 - 15:00
pg_checksums 1.0 released Version 1.0 of pg_checksums has been released. pg_checksums verifies, activates or deactivates data checksums in PostgreSQL instances. It is based on the pg_checksums utility in PostgreSQL 12, with the following additions: 1. Online verification of checksums The pg_checksums utility in PostgreSQL... 23-10 Michael Banck

Vik Fearing: pgDay Paris 2020 - Registration Open

23. Oktober 2019 - 10:00

Registration for pgDay Paris 2020 is now open.

We have some new ticket types this year, including a very cheap BLIND ticket that is only sold until the schedule is published. If you know you are coming to the conference no matter what, hurry up and grab one of these!

We also have cheap tickets this year for students and the unemployed. Valid proof is required.

Laurenz Albe: Never lose a PostgreSQL transaction with pg_receivewal

22. Oktober 2019 - 13:30

© Laurenz Albe 2019


“Durability”, the D of ACID, demands that a committed database transaction remains committed, no matter what. For normal outages like a power failure, this is guaranteed by the transaction log (WAL). However, if we want to guarantee durability even in the face of more catastrophic outages that destroy the WAL, we need more advanced methods.

This article discusses how to use pg_receivewal to maintain durability even under dire circumstances.

Vik Fearing: pgDay Paris 2020 - Call for Papers Open

22. Oktober 2019 - 10:00

The call for papers for pgDay Paris 2020 is now open. Submit your proposals for interesting talks about all things PostgreSQL, and join us in March!

Lætitia AVROT: SSO on Postgres with Active Directory : troubleshooting

22. Oktober 2019 - 2:00
Single Sign On (SSO) is a great security feature because if users don’t have to create many accounts and manage several passwords, they will agree on using a complex password more easily (or at least, we hope they do). The thing is, most of the time, companies use Active Directory to manage their accounts but Postgres usually works on Linux… And even if these two worlds can work together, it’s difficult to find people that master both environments.

Pavel Stehule: dll for plpgsql_check 1.7 are available for PostgreSQL 10, 11, and 12

20. Oktober 2019 - 23:10
I prepared dll libraries. You can load it from url

Pavel Stehule: precompiled libraries for orafce 3.8 for PostgreSQL 10, 11 and 12

20. Oktober 2019 - 11:55
I upload precompiled libraries to These libraries are 64bit only (there is not 32bit build for Postgres 11 and 12). For 32bit or older PostgreSQL releases, please, use older orafce builds. Windows build is partially reduced - there are not support for PLVlex for PostgreSQL 10 and 11 (due compilation problems), and there are not support for utl_file (due crash in these functions - I am not able to fix it on MSWIN platform).

Regina Obe: PostGIS 3.0.0

20. Oktober 2019 - 2:00

The PostGIS development team is pleased to release PostGIS 3.0.0.

This release works with PostgreSQL 9.5-12 and GEOS >= 3.6.

If you are using postgis_sfcgal extension, you need to compile against SFCGAL 1.3.1 or higher.

Best served with PostgreSQL 12 , GEOS 3.8.0 and pgRouting 3.0.0-beta.

Magnus Hagander: Nordic PGDay 2020 - Call for Papers open

18. Oktober 2019 - 17:15

The call for papers for Nordic PGDay 2020 in Helsinki, Finland, is now open. Submit your proposals for interesting talks about all things PostgreSQL, and join us in March.

Just like two years ago, the conference is held in cooperation with which is held two days later. So if you are interested in both, you can submit the same proposal to both conferences at once!

Alex Korban: Generating land-constrained geographical point grids with PostGIS

17. Oktober 2019 - 2:00
When I was in the market for an EV, one of the things I wondered about was how far I would be able to go outside the city before I had to charge it. Having a number for the range isn't enough to know offhand whether I'd be able to reach a particular destination. So I wanted to make the range more obvious in my EV guide by visualising vehicle range on a map. The trivial solution is to use range as a radius and show a circle: Distance circle But of course, that's going to be massively inaccur...

Regina Obe: PostGIS 3.0.0 coming soon - Try 3.0.0rc2 at a package repo near you

16. Oktober 2019 - 1:15

PostGIS 3.0.0 is planned for release early next week. In the meantime you will find PostGIS 3.0.0rc1 or rc2 available via,, and EDB Windows 64-bit stackbuilder for PostgreSQL 12.

Continue reading "PostGIS 3.0.0 coming soon - Try 3.0.0rc2 at a package repo near you"

Vasilis Ventirozos: Tuning checkpoints

15. Oktober 2019 - 23:52
We recently had the chance to help a customer with some IO related issues that ended up being unconfigured checkpoints. Something that may not always be obvious but can actually be somewhat common.

Let's start with how things roughly work.
Postgres smallest IO unit is a disk block that is 8kb (by default). Each time postgres needs a new block it will fetch it from the disks and load it to an area in RAM called shared_buffers.
When postgres needs to write, it does it in the same manner:

Rajeev Rastogi: An Overview of Various Auxiliary Plan Nodes in PostgreSQL

15. Oktober 2019 - 19:36

All modern database system supports a Query Optimizer module to automatically identify the most efficient strategy for executing the SQL queries. The efficient strategy is called “Plan” and it is measured in terms of cost which is directly proportional to “Query Execution/Response Time”.  The plan is represented in the form of a tree output from the Query Optimizer. The plan tree nodes can be majorly divided into the following 3 categories:

Hans-Juergen Schoenig: Prewarming PostgreSQL I/O caches

15. Oktober 2019 - 10:00

PostgreSQL uses shared_buffers to cache blocks in memory. The idea is to reduce
disk I/O and to speed up the database in the most efficient way
possible. During normal operations your database cache will be pretty useful and
ensure good response times. However, what happens if your database instance is
restarted – for whatever reason? Your PostgreSQL database performance will suffer
until your I/O caches have filled up again. This takes some time and it can
be pretty damaging to your query response times.