Re: [PATCH] Add pg_get_subscription_ddl() function

From: solai v <solai(dot)cdac(at)gmail(dot)com>
To: Vaibhav Dalvi <vaibhav(dot)dalvi(at)enterprisedb(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, alvherre(at)kurilemu(dot)de
Subject: Re: [PATCH] Add pg_get_subscription_ddl() function
Date: 2026-05-15 04:45:28
Message-ID: CAF0whucFJPgMfhfxrjniKJYKjStq_x7wX5A+phsQRaZn=4zv9Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi all,

I reviewed and tested the v8 patch on my current branch tree. The
patch functionality works correctly as expected after resolving manual
conflicts during patch application. After testing, I verified the
function availability for both name and oid variants, generated CREATE
SUBSCRIPTION DDL that appears syntactically valid and complete,
handling of invalid and NULL inputs, permission enforcement for
pg_read_all_data / pg_create_subscription, quoted identifier handling
for subscription/publication names and disabled subscription
reconstruction behavior. And tested logical replication setup with
publisher/subscriber clusters and verified the generated DDL syntax
appears correct and reusable. A few additional observations were also
noted that the connect=false behavior matches the documented rationale
and pg_dump behavior and the generated output currently emits all
subscription options, including default-valued ones.
Overall, the patch behaved correctly in my testing and looks good to me.

Regards,
Solai

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-05-15 04:55:17 Re: postgres_fdw: restore_stats uses current user's mapping instead of table owner's during ANALYZE
Previous Message solai v 2026-05-15 04:43:25 Re: Fix the race condition for updating slot minimum LSN