RE: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL
Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
From: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
To: 'Amit Kapila' <amit.kapila16@gmail.com>
Cc: Peter Smith <smithpb2250@gmail.com>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>, Önder Kalacı <onderkalaci@gmail.com>, Sergei Kornilov <sk@zsrv.org>
Date: 2023-07-11T07:17:50Z
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 →
-
Doc: Update the logical replication restriction w.r.t Replica Identity Full.
- 961cf5c9055f 17.0 landed
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