Neues vom PostgreSQL Planet
Hubert 'depesz' Lubaczewski: Finally – fixed time calculations for parallel plans in explain.depesz.com
Coming up with good index suggestion can be a complex task. It requires knowledge of both application queries and database specificities. Over the year multiple projects tried to solve this problem, one of which being PoWA with the version 3, with the help of pg_qualstats extension. It can give pretty good index suggestion, but it requires to install and configure PoWA, while some users wanted to only have the global index advisor.
“out of shared memory”: Some of you might have seen that error message in PostgreSQL already. But what does it really mean, and how can you prevent it? The problem is actually not as obscure as it might seem at first glance. max_locks_per_transaction is the critical configuration parameter you need to use to avoid trouble.
DigitalOcean is a cloud service provider, more of an IaaS (Infrastructure-as-a-Service) provider which is more suitable for small to medium scale businesses. You can get to know more about DigitalOcean here. What it does is a bit different to other cloud vendors like AWS or Azure and is not heavily global yet, take a look at this video which compares DigitalOcean with AWS.
Simple validation for tuple modification (insert/update/delete) is by applying constraints. More complex validation can be forced through trigger which is considered expensive by database experts.
The more efficient approach is by implementing validation in user defined function. Regular users are prevented from writing directly to table by issuing INSERT/UPDATE/DELETE. They must invoke provided function to perform those tasks.
© Laurenz Albe 2019
The biggest change in PostgreSQL v12 from the viewpoint of backward compatibility is that recovery.conf has been absorbed into postgresql.conf.
This article describes the changes and how you can adapt to them.Getting rid of recovery.conf
Up to now, the presence of the file recovery.conf was the trigger for PostgreSQL to go into recovery mode upon server start. In addition, the file contained all parameters to configure recovery, for example
plpgsql_check can detect some basic sql injection problems and has integrated profiler now. Lot of bug was fixed. These tools works well and I am almost satisfied with their functionality.
Today some lighter topic. I did screenshot of any theme supported by pspg. What theme do you use, or what theme do you prefer?
A lot has been written about configuring postgresql.conf, postgresql.auto.conf and so on. However, sometimes it requires to take a second look in order to understand, how PostgreSQL really handles configuration parameters. You will notice that PostgreSQL configuration offers more than meets the eye at first glance. So let us dive into PostgreSQL GUCs and configuration on a more theoretical level!
I'm pleased to introduce the latest release of phpPgAdmin, version 7.12.1.
This release incorporates the following changes:
- Fix a number of issues related to changes in Postgres 12.
- Fix an issue with truncation of long multibyte strings
- Removal of broken tree branches from table/view browse option
- Properly escape identifiers when browsing tables/views/schemas
- Add support for granting USAGE on sequences
Note this new version now requires support for the mbstring module in PHP.
Odds are you've been tasked with upgrading software from one major release to another at some point. Trust me, I understand how cumbersome and difficult these upgrades can be! Luckily, Crunchy Data has some tested methods to get you upgraded with the least amount of headache possible! For this use case, we’ll be using pg_upgrade. Let’s get started!