@@ -259,7 +259,7 @@ Branch: REL_10_STABLE [b6f869bee] 2022-02-11 15:23:52 -0500
259259 <para>
260260 The previous coding could try to read non-returnable columns
261261 in addition to the returnable ones. This was fairly harmless
262- because it didn't actually do anything with the bogus values;
262+ because it didn't actually do anything with the bogus values,
263263 but it fell foul of a recently-added error check that rejected
264264 such a plan.
265265 </para>
@@ -697,26 +697,6 @@ Branch: REL_10_STABLE [b5e060473] 2022-02-14 08:45:54 +0530
697697 <listitem>
698698<!--
699699Author: Tom Lane <tgl@sss.pgh.pa.us>
700- Branch: REL_12_STABLE [e16db75dd] 2022-02-15 12:21:28 -0500
701- Branch: REL_11_STABLE [efae4401c] 2022-02-15 12:21:28 -0500
702- Branch: REL_10_STABLE [17a8c4c3a] 2022-02-15 12:21:28 -0500
703- -->
704- <para>
705- Improve logical replication subscriber's error message for an
706- unsupported relation kind (Tom Lane)
707- </para>
708-
709- <para>
710- v13 and later servers support publishing partitioned tables. Older
711- server versions cannot handle subscribing to such a table, and they
712- gave a very misleading error message: <quote>table XYZ not found on
713- publisher</quote>. Arrange to deliver a more on-point message.
714- </para>
715- </listitem>
716-
717- <listitem>
718- <!--
719- Author: Tom Lane <tgl@sss.pgh.pa.us>
720700Branch: master [0fb6954aa] 2022-03-27 12:57:46 -0400
721701Branch: REL_14_STABLE [3f7a59c59] 2022-03-27 12:57:52 -0400
722702Branch: REL_13_STABLE [9016a2a3d] 2022-03-27 12:57:57 -0400