Re: Support logical replication of global object commands

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Zheng Li <zhengli10(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Support logical replication of global object commands
Date: 2023-02-16 06:32:16
Message-ID: CAA4eK1L8wd8XRrk83kx=5BM2EPreY2iM+Gx48Kn8z1ynxrK_wA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 30, 2022 at 8:09 AM Zheng Li <zhengli10(at)gmail(dot)com> wrote:
>
> > > I think a publication of ALL OBJECTS sounds intuitive. Does it mean we'll
> > > publish all DDL commands, all commit and abort operations in every
> > > database if there is such publication of ALL OBJECTS?
> > >
> >
> > Actually, I intend something for global objects. But the main thing
> > that is worrying me about this is that we don't have a clean way to
> > untie global object replication from database-specific object
> > replication.
>
> I think ultimately we need a clean and efficient way to publish (and
> subscribe to) any changes in all databases, preferably in one logical
> replication slot.
>

Agreed. I was thinking currently for logical replication both
walsender and slot are database-specific. So we need a way to
distinguish the WAL for global objects and then avoid filtering based
on the slot's database during decoding. I also thought about whether
we want to have a WALSender that is not connected to a database for
the replication of global objects but I couldn't come up with a reason
for doing so. Do you have any thoughts on this matter?

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2023-02-16 06:41:20 Re: DDL result is lost by CREATE DATABASE with WAL_LOG strategy
Previous Message Michael Paquier 2023-02-16 06:26:26 Re: Missing free_var() at end of accum_sum_final()?