On Wed, May 18, 2022 at 06:42:38PM +0200, Alvaro Herrera wrote: > On 2022-May-11, Justin Pryzby wrote: > > > I suggest to reference the mvcc docs from the merge docs, or to make the > > merge > > docs themselves include the referenced information. > > > > diff --git a/doc/src/sgml/ref/merge.sgml b/doc/src/sgml/ref/merge.sgml > > index f68aa09736c..99dd5814f36 100644 > > --- a/doc/src/sgml/ref/merge.sgml > > +++ b/doc/src/sgml/ref/merge.sgml > > @@ -544,6 +544,7 @@ MERGE <replaceable > > class="parameter">total_count</replaceable> > > <command>UPDATE</command> if a concurrent <command>INSERT</command> > > occurs. There are a variety of differences and restrictions between > > the two statement types and they are not interchangeable. > > + See <xref linkend="mvcc"/> for more information. > > Reading the paragraph, I think it may be better to do it the other way > around: first mention that concurrency is described in the MVCC page, > then explain that INSERT ON CONFLICT also exists. What do you think of > the attached?
Hmm, it seems odd to put "see also" first. My original complaint is that 1) merge.sgml doesn't include the detailed information; but 3) mentions it vaguely without linking to it: "There are a variety of differences and restrictions between the two statement types and they are not interchangeable." I prefer my original, but the most important thing is to include the link at *somewhere*. -- Justin