| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Hannu Krosing <hannuk(at)google(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Vitaly Davydov <v(dot)davydov(at)postgrespro(dot)ru>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Support logical replication of DDLs, take2 |
| Date: | 2026-04-29 11:29:26 |
| Message-ID: | CAFiTN-tPHaHRybrxJumKgMinhNE78bL2wXouPzH_vXnVnBsYYg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Wed, Apr 29, 2026 at 1:37 PM Hannu Krosing <hannuk(at)google(dot)com> wrote:
>
> On Wed, Apr 29, 2026 at 5:39 AM Dilip Kumar <dilipbalaut(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2026-04-29 12:10:17 | Re: Support logical replication of DDLs, take2 |
| Previous Message | Siraj G | 2026-04-29 09:04:49 | Re: Table and publisher/subscriber ownership |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2026-04-29 11:32:13 | Re: Include schema-qualified names in publication error messages. |
| Previous Message | Dilip Kumar | 2026-04-29 11:11:17 | Re: Include schema-qualified names in publication error messages. |