Horton
Menu

Re: Support logical replication of DDLs, take2

Dilip Kumar <dilipbalaut@gmail.com>

View thread
From: Dilip Kumar <dilipbalaut@gmail.com>
To: Hannu Krosing <hannuk@google.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Vitaly Davydov <v.davydov@postgrespro.ru>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-29T11:29:26Z
Lists: pgsql-hackers, pgsql-general 
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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add a run_as_owner option to subscriptions.

  2. Refactor pgoutput_change().

  3. Print the correct aliases for DML target tables in ruleutils.

  4. Fix object identity string for transforms

  5. Add grantable MAINTAIN privilege and pg_maintain role.

  6. Get rid of recursion-marker values in enum AlterTableType

  7. Release cache tuple when no longer needed

  8. Empty search_path in logical replication apply worker and walsender.

  9. Refactor format_type APIs to be more modular

  10. Use wrappers of PG_DETOAST_DATUM_PACKED() more.