From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
---|---|
To: | 'Shubham Khanna' <khannashubham1197(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | RE: Add support for specifying tables in pg_createsubscriber. |
Date: | 2025-07-28 05:07:21 |
Message-ID: | OSCPR01MB149664DEE1C8D02988E4666E9F55AA@OSCPR01MB14966.jpnprd01.prod.outlook.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Bapat | 2025-07-28 05:14:45 | Re: Document transition table triggers are not allowed on views/foreign tables |
Previous Message | Michael Paquier | 2025-07-28 04:22:04 | Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring |