Blog , p.2

December 28, 2021   •   News

Oleg Bartunov, CEO Postgres Professional and PostgreSQL Major Contributor gave a talk on JSONB performance at PGConf NYC 2021. After the presentation, EnterpriseDB’s Simon Riggs, another PostgreSQL Major Contributor proposed to create a PostgreSQL JSON workgroup (JSON Special Interest Group, JSIG). This group, consisting of several community members, will work together to enhance JSON functionality in Postgres for different use cases.

December 9, 2021   •   News

The Standard edition of Postgres Pro DBMS 14.1.1 has become available, along with new minor releases for the following versions: Std 9.6.24.1, Std 10.19.1, Std 11.14.1, Std 12.9.1 and Std 13.5.1.

November 11, 2021   •   News

PGConf.Russia Gathers 500+ IT Professionals at a Hybrid Online+Offline Event

25-26 October PGConf.Russia 2021 was held in a hybrid format to accommodate both online and offline participants. Postgres Professional organized this notable event for the 8th time; more than 500 people attended it virtually and in person. Software developers, database administrators, and top managers from the IT industry exchanged PostgreSQL best practices and shared their experience with the world’s most advanced open source database. Representatives of Intel, Yandex, EnterpriseDB, DBeaver Corp, Delivery Hero, and many other companies and organizations were speaking at PGConf.

October 11, 2021   •   PostgreSQL

This is a summary of Postgres Professional’s more than 6 years field experience of providing HA/DR solutions to our customers and it covers both PostgreSQL and Postgres Pro databases.

While most of our customers are making progress on their journeys to the cloud, many of the HA/DR solutions they use from the on-premises world can be used in the cloud as well.

September 27, 2021   •   PostgreSQL

During PostgreSQL maintenance, resource-consuming queries occur inevitably. Therefore, it's vital for every Database Engineer, DBA, or Software Developer to detect and fix them as soon as possible. In this article, we'll list various extensions and monitoring tools used to collect information about queries and display them in a human-readable way.

Then we will cover typical query writing mistakes and explain how to correct them. We will also consider cases where extended statistics are used for more accurate row count estimates. Finally, you will see an example of how PostgreSQL planner excludes redundant filter clauses during its work.

September 8, 2021   •   Company Updates

During our webinar on PostgreSQL query optimization, we found many of your questions interesting and helpful to the public, if properly answered. Get more useful links and working expert advice from Peter Petrov, our Database Engineer.

July 28, 2021   •   PostgreSQL

To remind you, we've already talked about relation-level locks, row-level locks, locks on other objects (including predicate locks) and interrelationships of different types of locks.

The following discussion of locks in RAM finishes this series of articles. We will consider spinlocks, lightweight locks and buffer pins, as well as events monitoring tools and sampling.

...

July 15, 2021   •   PostgreSQL

We've already discussed some object-level locks (specifically, relation-level locks), as well as row-level locks with their connection to object-level locks and also explored wait queues, which are not always fair.

We have a hodgepodge this time. We'll start with deadlocks (actually, I planned to discuss them last time, but that article was excessively long in itself), then briefly review object-level locks left and finally discuss predicate locks.

July 1, 2021   •   PostgreSQL

Last time, we discussed object-level locks and in particular relation-level locks. In this article, we will see how row-level locks are organized in PostgreSQL and how they are used together with object-level locks. We will also talk of wait queues and of those who jumps the queue.

June 17, 2021   •   PostgreSQL

The previous two series of articles covered isolation and multiversion concurrency control and logging.

In this series, we will discuss locks.

This series will consist of four articles:

  1. Relation-level locks (this article).
  2. Row-level locks.
  3. Locks on other objects and predicate locks.
  4. Locks in RAM.

 

June 3, 2021   •   PostgreSQL

In this blog post, we're explaining to those new to pg_profile why you might need this PostgreSQL extension in your daily work, on a real-world example.

May 13, 2021   •   PostgreSQL

So, we got acquainted with the structure of the buffer cache and in this context concluded that if all the RAM contents got lost due to failure, the write-ahead log (WAL) was required to recover. The size of the necessary WAL files and the recovery time are limited thanks to the checkpoint performed from time to time.

In the previous articles we already reviewed quite a few important settings that anyway relate to WAL. In this article (being the last in this series) we will discuss problems of WAL setup that are unaddressed yet: WAL levels and their purpose, as well as the reliability and performance of write-ahead logging.

April 23, 2021   •   PostgreSQL

We already got acquainted with the structure of the buffer cache — one of the main objects of the shared memory — and concluded that to recover after failure when all the RAM contents get lost, the write-ahead log (WAL) must be maintained.

The problem yet unaddressed, where we left off last time, is that we are unaware of where to start playing back WAL records during the recovery. To begin from the beginning, as the King from Lewis Caroll's Alice advised, is not an option: it is impossible to keep all the WAL records from the server start — this is potentially both a huge memory size and equally huge duration of the recovery. We need such a point that is gradually moving forward and that we can start the recovery at (and safely remove all the previous WAL records, accordingly). And this is the checkpoint, to be discussed below.

April 15, 2021   •   PostgreSQL

Last time we got acquainted with the structure of an important component of the shared memory — the buffer cache. A risk of losing information from RAM is the main reason why we need techniques to recover data after failure. Now we will discuss these techniques.

April 1, 2021   •   PostgreSQL
WAL in PostgreSQL: 1. Buffer Cache