Apa iku logical replication lan kapan iku migunani?

Question

Accepted Answer

**Logical replication** ngreplika data changes ing tingkat **tabel spesifik** (nggunakake model publish/subscribe), tinimbang nggawe salinan database cluster mau byte-for-byte kaya physical (streaming) replication. Iki ndadekake fleksibel — selektif, lintas versi, lan menyang schema beda — ideal kanggo migrasi lan integrasi.

## Logical vs physical replication

```text
PHYSICAL (streaming) → replicates the ENTIRE cluster at the storage/WAL level
  ✓ exact copy, simple   ✗ all-or-nothing, same Postgres version, read-only replica

LOGICAL → replicates specific TABLES' changes via a publish/subscribe model
  ✓ SELECTIVE (choose tables), CROSS-VERSION, to DIFFERENT schemas, replica is WRITABLE
  ✗ more setup, some limitations (DDL not replicated automatically, etc.)
```

## Nyetel logical replication (pub/sub)

```sql
-- on the SOURCE (publisher): publish specific tables
CREATE PUBLICATION my_pub FOR TABLE users, orders;
-- (or FOR ALL TABLES)

-- on the TARGET (subscriber): subscribe to the publication
CREATE SUBSCRIPTION my_sub
  CONNECTION 'host=source dbname=mydb user=rep'
  PUBLICATION my_pub;
-- → the subscriber receives and applies changes to users and orders
```

A **publication** nemtokake apa sing bakal direplika (tabel spesifik); a **subscription** ngkonsumsine. Perubahan (INSERT/UPDATE/DELETE) mili saka publisher menyang subscriber.

## Kapan logical replication iku migunani

```text
✓ ZERO-DOWNTIME MAJOR UPGRADES — replicate from an old version to a new version, then
  switch over (physical replication can't cross versions) — a key use case
✓ MIGRATIONS — move data to a new server/cluster with minimal downtime
✓ SELECTIVE replication — replicate only certain tables (not the whole database)
✓ INTEGRATIONS — feed specific data to another system (analytics, data warehouse)
✓ Consolidating data from multiple databases into one
✓ The replica is WRITABLE (can have its own additional data/tables)
```

## Apa sing penting

Logical replication iku katrangan PostgreSQL sing berharga kanggo **skenario replikasi data fleksibel** — utamane migrasi, upgrade, lan integrasi — mula ngerti iku migunani kanggo katrangan tingkat senior kanggo database operations lan architecture.

Bedane kunci saka physical (streaming) replication iku **fleksibilitas**: tinimbang nggawe salinan cluster mau byte-for-byte (physical), logical replication ngreplika **tabel spesifik** via publish/subscribe, lan sing penting bisa ngoperate **lintas versi PostgreSQL** lan menyang **schema beda**, kanthi **writable** subscriber.

Fleksibilitas iki ngaktifake use case penting sing physical replication ora bisa gawe: paling mburi **zero-downtime major version upgrade** (ngreplika saka versi Postgres lawas menyang sing anyar, banjur ngalih — kapabilitas kritis amarga physical replication mbutuhake versi sama, ndadekake logical replication metode standar kanggo upgrade versi majore tanpa downtime), **migrasi** (mindhah data menyang server/cluster anyar kanthi downtime minimal), **replikasi selektif** (ngreplika mung tabel tertentu), lan **integrasi** (menehi data spesifik menyang sistem analytics, data warehouse, utawa database liyane).

Ngerti setup publish/subscribe (publikasi nemtokake apa sing direplika, subscription ngkonsumsine) lan use case sing cocok (utamane upgrade lan migrasi) ngrefleksikake katrangan operational sing berharga.

Samarga upgrade versi majore lan migrasi kanthi downtime minimal iku penting, tantangan operational nyata (lan logical replication iku alat kunci kanggo iku), lan amarga replikasi selektif/lintas sistem ngaktifake pola integrasi sing berharga, ngerti logical replication — cara bedane saka physical, fleksibilitas (lintas versi, selektif, writable), lan use case (utamane zero-downtime upgrade lan migrasi) — iku katrangan tingkat senior sing berharga kanggo PostgreSQL operations lan architecture, utamane relevan kanggo kabutuhan umum, high-stakes kanggo upgrade lan migrasi database tanpa downtime, topik sing nunjukake ngerti maju babagan Postgres deployment lan operations.