RE: Add support for specifying tables in pg_createsubscriber.

Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>

From: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>

To: 'Shubham Khanna' <khannashubham1197@gmail.com>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-07-28T05:07:21Z

Lists: pgsql-hackers

Commits

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

Support existing publications in pg_createsubscriber.
- 85ddcc2f4cde 19 (unreleased) landed

Dear Shubham,

> The attached patch introduces a new '--table' option that can be
> specified after each '--database' argument.

Do we have another example which we consider the ordering of options? I'm unsure
for it. Does getopt_long() always return parsed options with the specified order?

> The syntax is like that used in 'vacuumdb'
> and supports multiple '--table' arguments per database, including
> optional column lists and row filters.

Vacuumdb nor pg_restore do not accept multiple --database, right?
I'm afraid that current API has too complex.

Per document:
```
+     <term><option>-f <replaceable class="parameter">table</replaceable></option></term>
+     <term><option>--table=<replaceable class="parameter">table</replaceable></option></term>
```

I feel using "-f" is not suitable. Let's remove the shorten option now.

Best regards,
Hayato Kuroda
FUJITSU LIMITED