Here's a toast to PostgreSQL for clinching DB-Engines’ DBMS of the Year title for the fourth time!
Hello, database warriors! In this article, we're deepening our exploration into Fujitsu Enterprise Postgres and PostgreSQL security by focusing on access control. Remember, this involves two key elements: authentication, the process verifying identities, and authorization, the system determining access levels.
Hey there, database gurus! In our journey through the world of database security, today we're taking a focused dive into one example from the CIS Benchmark for PostgreSQL 16 – Section 4.4 on revoking excessive Data Manipulation Language (DML) privileges.
Hey database dynamos! After diving into the critical security roles in our last chat, let's switch gears and talk about something that can really set the stage for solid database security - security benchmarks.
Hey there, database defenders! As we embark on this detailed exploration into the world of database security, it's crucial to understand the various security roles within an organization, and that is what this blog post is about.
Our team is further extending its commitment to database security education through a new blog series featured right here.
I find it very important to try to live with purpose, as it gives me a sense of direction and motivation in life. Can this outlook also be applied to a database? Is PostgreSQL a purpose driven database?
Fujitsu has introduced a new feature in Fujitsu Enterprise Postgres called policy-based login security. In this blog, I will delve into this new feature and how to implement it.
Fujitsu Enterprise Postgres 15 SP1 was released in the beginning of this month. This release includes new capabilities which have been developed based on customer conversations and requirements we have been observing in the market.
Geospatial data is an essential component of modern-day mapping and location-based services, assisting with decision making around complex problems, and in the case of open-source geo data, also fostering the transparency of governments and institutions.
Earlier this year, I was in Canada for PGConf 2023, where I talked about the evolution of PostgreSQL from a Berkeley research project to its current status as the most advanced open-source database, and discussed the various changes introduced for PostgreSQL 16, particularly regarding logical replication.
In this blog post, I will give a brief introduction to a new PostgreSQL 16 feature that allows bi-directional replication by filtering by origin.
As a PostgreSQL DBA, we commonly hear and use the term "dead rows" and "bloat." In this blog post, I'd like to talk about these concepts as well as "transaction wraparound," one of the most dangerous situations in PostgreSQL. I'll also outline how to handle this problem with an example.
The latest PostgreSQL 15 release brings significant improvements to logical replication, which fortifies CREATE/ ALTER PUBLICATION capabilities, and benefits by enhancing security, improving ease of use, and reducing network traffic.
PostgreSQL 15 introduced a crucial change regarding permission checks in logical replication, to avoid a potential security violation. Let me show you how this improvement works.
