Re: Minimal logical decoding on standbys

From: Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com>
To: Andreas Joseph Krogh <andreas(at)visena(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Minimal logical decoding on standbys
Date: 2020-01-21 02:57:42
Message-ID: CAJ3gD9e--=5wL1odKqg3TWt41y5gUJvBBT+gW0PVnujgZdvhAw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 17 Jan 2020 at 13:20, Andreas Joseph Krogh <andreas(at)visena(dot)com> wrote:
>
> På torsdag 16. januar 2020 kl. 05:42:24, skrev Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com>:
>
> On Fri, 10 Jan 2020 at 17:50, Rahila Syed <rahila(dot)syed(at)2ndquadrant(dot)com> wrote:
> >
> > Hi Amit,
> >
> > Can you please rebase the patches as they don't apply on latest master?
>
> Thanks for notifying. Attached is the rebased version.
>
>
> Will this patch enable logical replication from a standby-server?

Sorry for the late reply.
This patch only supports logical decoding from standby. So it's just
an infrastructure for supporting logical replication from standby. We
don't support creating a publication from standby, but the publication
on master is replicated on standby, so we might be able to create
subscription nodes that connect to existing publications on standby,
but basically we haven't tested whether the publication/subscription
model works with a publication on a physical standby. This patch is
focussed on providing a way to continue logical replication *after*
the standby is promoted as master.

--
Thanks,
-Amit Khandekar
EnterpriseDB Corporation
The Postgres Database Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2020-01-21 02:59:18 Re: Psql patch to show access methods info
Previous Message Craig Ringer 2020-01-21 01:44:12 Re: Physical replication slot advance is not persistent