ru
Feedback
PostgreSQL DBA

PostgreSQL DBA

Открыть в Telegram

Sharing knowledge about postgresql database

Больше
2 024
Подписчики
-124 часа
+17 дней
-730 день
Архив постов
Bitmap Scans (Bitmap Index Scan, Bitmap Heap Scan): Used when multiple indexes might apply to a query. The database creates bitmaps representing rows matching each index condition and then combines these bitmaps before fetching the rows from the table. Can be useful when combining multiple filter conditions.

Index Scans (Index Scan, Index Only Scan): Using an index to locate rows. Index Scan requires fetching the actual row data from the table after using the index, while Index Only Scan can retrieve all necessary data directly from the index itself (highly efficient).

Sequential Scans (Seq Scan): Reading the entire table row by row. This is generally inefficient for large tables, especially when filtering on specific columns. Indicates a lack of suitable indexes or that the planner determined an index scan would be more expensive.

photo content

photo content

photo content

photo content

photo content

photo content

The Zero-RPO Stack
The Zero-RPO Stack

Zero-RPO PostgreSQL Configuration — Complete Guide RPO (Recovery Point Objective) = maximum acceptable data loss measured in
Zero-RPO PostgreSQL Configuration — Complete Guide RPO (Recovery Point Objective) = maximum acceptable data loss measured in time. Zero-RPO means zero data loss — every committed transaction must survive a primary failure.

Failover is the process of promoting a replica to become the new primary when the original primary fails. Here's a full break
Failover is the process of promoting a replica to become the new primary when the original primary fails. Here's a full breakdown covering manual, automated, and pglogical-aware failover.

A replication set defines which tables and sequences to replicate: -- Create a named replication set SELECT pglogical.create_replication_set( set_name := 'my_replication_set', replicate_insert := true, replicate_update := true, replicate_delete := true, replicate_truncate := true ); -- Add specific tables to the set SELECT pglogical.replication_set_add_table( set_name := 'my_replication_set', relation := 'public.orders', synchronize_data := true -- Initial data copy ); SELECT pglogical.replication_set_add_table('my_replication_set', 'public.customers', true); SELECT pglogical.replication_set_add_table('my_replication_set', 'public.products', true); -- Add ALL tables in a schema at once SELECT pglogical.replication_set_add_all_tables( set_name := 'my_replication_set', schema_names := ARRAY['public'], synchronize_data := true ); -- Add sequences SELECT pglogical.replication_set_add_sequence( set_name := 'my_replication_set', relation := 'public.orders_id_seq', synchronize_data := true ); -- Add ALL sequences SELECT pglogical.replication_set_add_all_sequences('my_replication_set', ARRAY['public'], true);

pglogical Setup — Step by Step
pglogical Setup — Step by Step

Installation pglogical
Installation pglogical

Architecture Overview
Architecture Overview

pglogical is a PostgreSQL extension that provides logical replication with more features than built-in logical replication —
pglogical is a PostgreSQL extension that provides logical replication with more features than built-in logical replication — including DDL replication, conflict handling, and row/column filtering.

Quick Decision Guide
Quick Decision Guide

photo content

photo content