PostgreSQL Performance & Query Optimization · Aula

Estratégias de replicação (por fluxo e lógica)

Entenda e configure vários métodos de replicação, como a replicação por fluxo e a replicação lógica, para garantir alta disponibilidade e ampliar a capacidade de leitura.

Estratégias de replicação (por fluxo e lógica) é uma aula grátis de PostgreSQL Performance & Query Optimization no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de PostgreSQL Performance & Query Optimization, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de PostgreSQL Performance & Query Optimization inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Why Data Replication?

Imagine your database goes down! Replication is key to preventing data loss and ensuring your application stays online. It creates copies of your database.

It's vital for:

High Availability (HA): If the main server fails, a copy can take over.
Read Scaling: Distribute read queries across multiple servers, reducing load on the primary.

The Primary-Replica Setup

The most common replication setup is a Primary-Replica (or Master-Slave) model. One database server acts as the primary, handling all writes.

Primary: Processes all write operations (INSERT, UPDATE, DELETE).
Replica(s): Receive copies of data changes from the primary and can serve read-only queries.

This ensures data consistency and offloads read traffic.

Streaming Replication: The Basics

Streaming Replication is PostgreSQL's built-in, physical replication method. It works by continuously shipping the Write-Ahead Log (WAL) records from the primary to one or more replicas.

WAL records are low-level descriptions of every change made to the database. Replicas apply these changes to stay in sync.

WAL Shipping in Action

Here's how streaming replication works:

The primary server writes all database changes to its WAL files.
A dedicated process (WAL sender) on the primary sends these WAL records to replica servers.
A process (WAL receiver) on each replica receives and applies these records.

This keeps the replica's data identical to the primary's, block by block.

Setting Up Streaming Replication (Primary)

To enable streaming replication on the primary, you need to configure postgresql.conf:

wal_level = replica (or higher)
max_wal_senders = 10 (number of replicas/connections)
listen_addresses = '*' (allow connections from replicas)

You'll also need to set up pg_hba.conf to allow replica connections.

ALTER SYSTEM SET wal_level = 'replica';
ALTER SYSTEM SET max_wal_senders = 10;
ALTER SYSTEM SET listen_addresses = '*';

-- After these, restart PostgreSQL

Initializing a Replica with pg_basebackup

Before a replica can stream WAL, it needs a full copy of the primary's data. pg_basebackup is the standard tool for this.

It creates a consistent snapshot of the primary's data directory, which then becomes the replica's initial data.

pg_basebackup -h primary_host -p 5432 -U replication_user -D /var/lib/postgresql/data_replica -F p -Xs stream -P

Configuring the Replica

After pg_basebackup, the replica needs a few files:

A standby.signal file in its data directory (for PostgreSQL 12+).
A postgresql.conf with hot_standby = on (if you want to run queries).
A primary_conninfo setting in postgresql.conf to tell it where to connect to the primary.

This allows it to start up and connect as a replica.

ALTER SYSTEM SET hot_standby = 'on';
ALTER SYSTEM SET primary_conninfo = 'host=primary_host port=5432 user=replication_user password=your_password';

-- Create an empty standby.signal file:
touch /var/lib/postgresql/data_replica/standby.signal

-- Then start the replica PostgreSQL instance

Logical Replication: A Different Approach

Logical Replication is a newer, more flexible replication method introduced in PostgreSQL 10. Unlike streaming replication, it replicates data based on its logical representation (row changes, not physical blocks).

This allows for selective replication of tables or even databases, and cross-version/cross-platform replication.

Publications and Subscriptions

Logical replication uses a publish-subscribe model:

A Publication is created on the primary, defining which tables or changes to publish.
A Subscription is created on the replica, defining which publications to subscribe to.

The primary then sends logical decoding output (changes) to the subscribers, which apply them.

Setting Up Logical Replication (Example)

Here's a simplified example of setting up logical replication:

On Primary:

CREATE PUBLICATION my_pub FOR TABLE my_table;

On Replica:

CREATE SUBSCRIPTION my_sub CONNECTION 'host=primary_host dbname=mydb user=repl_user password=xyz' PUBLICATION my_pub;

Remember to configure wal_level = logical and max_replication_slots on the primary.

ALTER SYSTEM SET wal_level = 'logical';
ALTER SYSTEM SET max_replication_slots = 5;

-- On Primary:
CREATE PUBLICATION my_pub FOR TABLE my_table;

-- On Replica:
CREATE SUBSCRIPTION my_sub CONNECTION 'host=primary_host dbname=mydb user=repl_user password=xyz' PUBLICATION my_pub;

Replication Strategy Check

You need to set up replication for a PostgreSQL database. You want an exact, block-for-block copy of your entire database on a standby server for high availability. Which replication method is best suited for this goal?

Recap: Streaming vs. Logical

We've explored two key PostgreSQL replication strategies:

Streaming Replication: A physical, continuous copy of the entire database using WAL files. Great for high availability and read scaling with identical replicas.
Logical Replication: A flexible, publish-subscribe model replicating logical changes (rows). Ideal for selective replication, cross-version upgrades, or integrating with other systems.

Choosing the right strategy depends on your specific needs for consistency, flexibility, and performance.

Perguntas Frequentes

A aula “Estratégias de replicação (por fluxo e lógica)” é grátis?

Sim — o texto completo de “Estratégias de replicação (por fluxo e lógica)” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de PostgreSQL Performance & Query Optimization, atualize para CoddyKit PRO. O curso de PostgreSQL Performance & Query Optimization inclui 4 aulas no total.

O que vou aprender em “Estratégias de replicação (por fluxo e lógica)”?

Entenda e configure vários métodos de replicação, como a replicação por fluxo e a replicação lógica, para garantir alta disponibilidade e ampliar a capacidade de leitura. Você pratica PostgreSQL Performance & Query Optimization com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar PostgreSQL Performance & Query Optimization?

Nenhuma experiência prévia é necessária. PostgreSQL Performance & Query Optimization no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.

Quanto tempo leva a aula “Estratégias de replicação (por fluxo e lógica)”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de PostgreSQL Performance & Query Optimization?

Sim. Cada aula de PostgreSQL Performance & Query Optimization inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

Agrupamento de conexões com PgBouncer
Estratégias de replicação (por fluxo e lógica)
Fragmentação e PostgreSQL distribuído
Escalabilidade de leitura com Hot Standby e balanceamento de carga

← Voltar para PostgreSQL Performance & Query Optimization