RE: locking [user] catalog tables vs 2pc vs logical rep
От | osumi.takamichi@fujitsu.com |
---|---|
Тема | RE: locking [user] catalog tables vs 2pc vs logical rep |
Дата | |
Msg-id | OSBPR01MB488875D57A15C4E5391A81BCED0A9@OSBPR01MB4888.jpnprd01.prod.outlook.com обсуждение исходный текст |
Ответ на | RE: locking [user] catalog tables vs 2pc vs logical rep ("osumi.takamichi@fujitsu.com" <osumi.takamichi@fujitsu.com>) |
Ответы |
Re: locking [user] catalog tables vs 2pc vs logical rep
|
Список | pgsql-hackers |
On Sunday, June 20, 2021 9:50 PM I wrote: > On Sunday, June 20, 2021 3:23 PM Amit Kapila <amit.kapila16@gmail.com> > wrote: > > On Sun, Jun 20, 2021 at 9:28 AM osumi.takamichi@fujitsu.com > > <osumi.takamichi@fujitsu.com> wrote: > > > * doc/src/sgml/logicaldecoding.sgml > ... > > > > > > Now we have the four paren supplementary descriptions, not to make > > > users miss any other [user] catalog tables. > > > Because of this, the built output html gives me some redundant > > > impression, for that parts. Accordingly, couldn't we move them to > > > outside of the itemizedlist section in a simple manner ? > > > > > > For example, to insert a sentence below the list, after removing the > > > paren descriptions in the listitem, which says "Note that those > > > commands that can cause deadlock apply to not only explicitly > > > indicated system catalog tables above but also any other [user] catalog > table." > > > > Sounds reasonable to me. /but also any other/but also to any other/, > > to seems to be missing in the above line. Kindly send an update patch. > Excuse me, I don't understand the second sentence. > I wrote "but also" clause in my example. > > Also, attached the patch for the change to the HEAD. I've updated the patch to follow the correction Amit-san mentioned. Please check. Best Regards, Takamichi Osumi
Вложения
В списке pgsql-hackers по дате отправления: