| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Önder Kalacı <onderkalaci(at)gmail(dot)com>, Sergei Kornilov <sk(at)zsrv(dot)org> |
| Subject: | RE: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL |
| Date: | 2023-07-11 07:17:50 |
| Message-ID: | TYAPR01MB586674CEA8531C71C809F763F531A@TYAPR01MB5866.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Amit,
> After seeing this, I am thinking about whether we add this restriction
> on the Subscription page [1] or Restrictions page [2] as proposed. Do
> you others have any preference?
>
> [1] -
> https://www.postgresql.org/docs/devel/logical-replication-subscription.html
> [2] -
> https://www.postgresql.org/docs/devel/logical-replication-restrictions.html
Thanks for giving suggestion. But I still think it should be at "Restrictions" page
because all the limitation has been listed that page.
Moreover, the condition of this limitation is not closed to subscriber - the setup
on publisher is also related. I think such descriptions it may cause readers
to be confused.
But anyway, I have never been in mind such a point of view.
Maybe I should hear Sergei's opinion. Thought?
Best Regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2023-07-11 07:37:00 | Re: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL |
| Previous Message | Kyotaro Horiguchi | 2023-07-11 07:16:09 | Re: add non-option reordering to in-tree getopt_long |