Re: PostgreSQL Logical decoding

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Ankit Oza <ankit(dot)p(dot)oza(at)gmail(dot)com>
Cc: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL Logical decoding
Date: 2022-10-12 06:14:12
Message-ID: CAA4eK1LDuH2fdCpa683ySZ1H7dBBWOHnqs2+R4g4Jih3NtePeQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 12, 2022 at 10:09 AM Ankit Oza <ankit(dot)p(dot)oza(at)gmail(dot)com> wrote:
>
> Thanks Ashutosh,
>
> Actually we use the Postgres service offered by Azure (Flexible server). So, I was looking at the following documentation which talks about Logical Replication and Logical Decoding as two different methods of replication. Here Logical replication talks about creating both Publisher and Subscriber settings using simple SQL statements. While for Logical decoding its talking about publishing WAL but not on how to consume this WAL.
> Logical replication and logical decoding - Azure Database for PostgreSQL - Flexible Server | Microsoft Learn
>
> Also Logical Replication has some limitations like materialized views, sequences being not replicated. While DDL changes propagation is a common deficiency among both Logical decoding and Logical Replication. Am I reading this correctly?
> PostgreSQL: Documentation: 12: 30.4. Restrictions
>
> With this reading I thought Logical decoding may be the way to go. However please guide us on our understanding.
>

Those restrictions (sequences, materialized views, etc.) apply to
logical decoding as well. We don't support decoding operations on
those objects.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Drouvot, Bertrand 2022-10-12 06:17:14 Re: Patch proposal: make use of regular expressions for the username in pg_hba.conf
Previous Message Masahiko Sawada 2022-10-12 06:10:50 Re: test_decoding assertion failure for the loss of top-sub transaction relationship