| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Peter Smith' <smithpb2250(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: Review items for EXCEPT TABLE publication |
| Date: | 2026-09-14 05:34:25 |
| Message-ID: | OS9PR01MB121492F74E19535A33D820B6BF5BB2@OS9PR01MB12149.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Peter,
> Looks good, but isn't it more common for an errhint to say what
> command to use instead of just "make this happen"?
>
> e.g.
> "First use ALTER PUBLICATION ... to drop the table from the
> publication, or to remove it from the publication's EXCEPT clause."
Possible, but other lines refer the FULL command in the notation. Like
ALTER TABLE ... ALTER CONSTRAINT ... INHERIT,
ALTER DATABASE ... REFRESH COLLATION VERSION,
ALTER SUBSCRIPTION ... SET PUBLICATION ... WITH (refresh = false).
Based on that current style may be more appropriate unless exact commands
are referred there.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2026-09-14 05:43:02 | Re: Review items for EXCEPT TABLE publication |
| Previous Message | Michael Paquier | 2026-09-14 05:12:18 | Re: Support for 8-byte TOAST values, round two |