Re: Support logical replication of DDLs, take2 - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Support logical replication of DDLs, take2
Date
Msg-id CAFiTN-tPHaHRybrxJumKgMinhNE78bL2wXouPzH_vXnVnBsYYg@mail.gmail.com
Whole thread
In response to Re: Support logical replication of DDLs, take2  (Hannu Krosing <hannuk@google.com>)
List pgsql-hackers
On Wed, Apr 29, 2026 at 1:37 PM Hannu Krosing <hannuk@google.com> wrote:
>
> On Wed, Apr 29, 2026 at 5:39 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:

> > Another question is
> > what we would do with those deparsed representations: will we convert
> > them to SQL on the subscriber and execute, or do something else?
>
> Current pg_dump approach is logically equivalent to "doing it on the
> subscriber", pg_dump is designed to dump schemas from all older
> database versions in format that is compatible with the version the
> pg_dump is written for.

IIUC, you're suggesting a pg_dump-style mechanism for SQL generation
from the catalog. My concern is that pg_dump is snapshot-based, while
decoding is incremental.  So how to we generate SQL from the catalog
for incremental changes(like an ALTER TABLE...SET DATA TYPE)?

--
Regards,
Dilip Kumar
Google



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Include schema-qualified names in publication error messages.
Next
From: shveta malik
Date:
Subject: Re: Include schema-qualified names in publication error messages.