It can also be used for use cases like security and geo-fencing of data for regulatory compliance, implementation of multi-tenancy, and stripping off personally identifiable information for reporting purposes. This selective replication is not just helpful for performance gains (in case not all data needs to be replicated). Row and column level filters help you selectively replicate data from your primary database to your standby. With v15, logical replication adds the much-awaited feature of row and column-level filters.
Before v10, logical replication could only be achieved with the help of the extension, pglogical. Since then, it has taken strides and added lots of enhancements and functionality in-core. Logical Replication was added to core PostgreSQL in version 10. Row and column filters in logical replication
#Postgresql 13 code
MERGE has been around in Oracle and SQL Server for a while, and an interesting benefit that the implementation in PostgreSQL brings is that it makes it easier for people to move their SQL code from Oracle to PostgreSQL. Reducing the LOC count also reduces the maintenance overhead over the long term. The business logic that would have otherwise required many Lines of Code (LOC) is made simple with this conditional statement. The graphic below is a simple representation of the statement. Part of the SQL Standard and focusing on making the developer’s job easier, the MERGE command is a very useful enhancement, making it simple to conditionally insert, update, or delete data. I describe below some of the features that I find especially exciting. v15, has loads of new features and enhancements to offer. As always, this year’s major version, i.e. PostgreSQL Global Development Group (PGDG) has been really good about releasing one major version and four minor versions each year. If all goes well – fingers crossed! – this release will be promoted to General Availability (or GA) on October 13.
After four beta releases and one Release Candidate, the RC2 for PostgreSQL 15 was announced earlier today.
0 kommentar(er)
