> I think that there are some (possibly) tricky challenges that haven't
> been discussed yet to support replicating global objects.
>
> First, as for publications having global objects (roles, databases,
> and tablespaces), but storing them in database specific tables like
> pg_publication doesn't
ands can be executed in any database.
> 2. Global objects are not schema qualified.
> 3. Global object commands are not captured by event triggers.
>
> I’ve put together a prototype to support logical replication of global
> object commands in the attached patch. This patch builds on
On Fri, Feb 17, 2023 at 4:48 AM Amit Kapila wrote:
>
> On Fri, Feb 17, 2023 at 10:58 AM Zheng Li wrote:
> >
> > > > > 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 rep
On Fri, Feb 17, 2023 at 10:58 AM Zheng Li wrote:
>
> > > > 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.
> >
> > > 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
On Thu, Feb 16, 2023 at 12:02 PM Amit Kapila wrote:
>
> On Tue, Aug 30, 2022 at 8:09 AM Zheng Li 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 the
On Tue, Aug 30, 2022 at 8:09 AM Zheng Li 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 so
> > 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 worryi
On Tue, Aug 16, 2022 at 11:35 AM Zheng Li wrote:
>
> > Can we think of relying to send WAL of such DDLs just based on whether
> > there is a corresponding publication (ex. publication of ALL OBJECTS)?
> > I mean avoid database-specific filtering in decoding for such DDL
> > commands but not sure h
> Can we think of relying to send WAL of such DDLs just based on whether
> there is a corresponding publication (ex. publication of ALL OBJECTS)?
> I mean avoid database-specific filtering in decoding for such DDL
> commands but not sure how much better it is than the current proposal?
I think a p
ct. These
> > commands are different from other DDL commands in that:
> >
> > 1. Global object commands can be executed in any database.
> > 2. Global objects are not schema qualified.
> > 3. Global object commands are not captured by event triggers.
> >
>
can be executed in any database.
> 2. Global objects are not schema qualified.
> 3. Global object commands are not captured by event triggers.
>
> I’ve put together a prototype to support logical replication of global
> object commands in the attached patch. This patch builds on the
not captured by event triggers.
I’ve put together a prototype to support logical replication of global
object commands in the attached patch. This patch builds on the DDL
replication patch from ZJ in [2] and must be applied on top of it.
Here is a list of global object commands that the patch
13 matches
Mail list logo
