Copy-edit docs for logical replication column lists

There was a excessive structure, leading to somewhat disorganized
presentation of the information. Remove a few tags and reorder
paragraphs to make the text flow more easily.  Also, reword some of it
to be more concise.

The bit about column list combination is not modified, other than to
remove an uninteresting (and IMO confusing and wrong) paragraph; I
intend to deal with it differently afterwards.

Backpatch to 15.

Discussion: https://postgr.es/m/20220913121138.yn7ekkfysxzhkm2u@alvherre.pgsql

doc/src/sgml/logical-replication.sgml

@@ -1093,44 +1093,39 @@ test_sub=# SELECT * FROM child ORDER BY a;
   <title>Column Lists</title>
 
   <para>
-   By default, all columns of a published table will be replicated to the
+   Each publication can optionally specify which columns of each table are
-   appropriate subscribers. The subscriber table must have at least all the
+   replicated to subscribers. The table on the subscriber side must have at
-   columns of the published table. However, if a
+   least all the columns that are published. If no column list is specified,
-   <firstterm>column list</firstterm> is specified then only the columns named
+   then all columns in the publisher are replicated.
-   in the list will be replicated. This means the subscriber-side table only
+   See <xref linkend="sql-createpublication"/> for details on the syntax.
-   needs to have those columns named by the column list. A user might choose to
-   use column lists for behavioral, security or performance reasons.
   </para>
 
-  <sect2 id="logical-replication-col-list-rules">
-   <title>Column List Rules</title>
-
   <para>
-    A column list is specified per table following the table name, and enclosed
+   The choice of columns can be based on behavioral or performance reasons.
-    by parentheses. See <xref linkend="sql-createpublication"/> for details.
+   However, do not rely on this feature for security: a malicious subscriber
+   is able to obtain data from columns that are not specifically
+   published.  If security is a consideration, protections can be applied
+   at the publisher side.
   </para>
 
   <para>
-    When specifying a column list, the order of columns is not important. If no
+   If no column list is specified, any columns added later are automatically
-    column list is specified, all columns of the table are replicated through
+   replicated. This means that having a column list which names all columns
-    this publication, including any columns added later. This means a column
+   is not the same as having no column list at all.
-    list which names all columns is not quite the same as having no column list
-    at all. For example, if additional columns are added to the table then only
-    those named columns mentioned in the column list will continue to be
-    replicated.
   </para>
 
   <para>
-    Column lists have no effect for <literal>TRUNCATE</literal> command.
+   A column list can contain only simple column references.  The order
+   of columns in the list is not preserved.
   </para>
 
-  </sect2>
-
-  <sect2 id="logical-replication-col-list-restrictions">
-   <title>Column List Restrictions</title>
-
   <para>
-    A column list can contain only simple column references.
+   For partitioned tables, the publication parameter
+   <literal>publish_via_partition_root</literal> determines which column list
+   is used. If <literal>publish_via_partition_root</literal> is
+   <literal>true</literal>, the root partitioned table's column list is used.
+   Otherwise, if <literal>publish_via_partition_root</literal> is
+   <literal>false</literal> (the default), each partition's column list is used.
   </para>
 
   <para>
@@ -1139,43 +1134,19 @@ test_sub=# SELECT * FROM child ORDER BY a;
    table's replica identity columns (see
    <xref linkend="sql-altertable-replica-identity"/>).
    If a publication publishes only <command>INSERT</command> operations, then
-    the column list is arbitrary and may omit some replica identity columns.
+   the column list may omit replica identity columns.
-   </para>
-
-  </sect2>
-
-  <sect2 id="logical-replication-col-list-partitioned">
-   <title>Partitioned Tables</title>
-
-   <para>
-    For partitioned tables, the publication parameter
-    <literal>publish_via_partition_root</literal> determines which column list
-    is used. If <literal>publish_via_partition_root</literal> is
-    <literal>true</literal>, the root partitioned table's column list is used.
-    Otherwise, if <literal>publish_via_partition_root</literal> is
-    <literal>false</literal> (default), each partition's column list is used.
   </para>
 
-  </sect2>
-
-  <sect2 id="logical-replication-col-list-initial-data-sync">
-   <title>Initial Data Synchronization</title>
-
   <para>
-    If the subscription requires copying pre-existing table data and a
+   Column lists have no effect for the <literal>TRUNCATE</literal> command.
-    publication specifies a column list, only data from those columns will be
-    copied.
   </para>
 
-   <note>
   <para>
-     If the subscriber is in a release prior to 15, copy pre-existing data
+   During initial data synchronization, only the published columns are
-     doesn't use column lists even if they are defined in the publication.
+   copied.  However, if the subscriber is from a release prior to 15, then
-     This is because old releases can only copy the entire table data.
+   all the columns in the table are copied during initial data synchronization,
+   ignoring any column lists.
   </para>
-   </note>
-
-  </sect2>
 
   <sect2 id="logical-replication-col-list-combining">
    <title>Combining Multiple Column Lists</title>
@@ -1193,12 +1164,6 @@ test_sub=# SELECT * FROM child ORDER BY a;
      <literal>ALTER SUBSCRIPTION ... DROP PUBLICATION</literal> and then add it
      back after adjusting the column list.
     </para>
-    <para>
-     Background: The main purpose of the column list feature is to allow
-     statically different table shapes on publisher and subscriber, or hide
-     sensitive column data. In both cases, it doesn't seem to make sense to
-     combine column lists.
-    </para>
    </warning>
 
   </sect2>

doc/src/sgml/ref/create_publication.sgml

@@ -94,7 +94,7 @@ CREATE PUBLICATION <replaceable class="parameter">name</replaceable>
       effect on <literal>TRUNCATE</literal> commands. See
       <xref linkend="logical-replication-col-lists"/> for details about column
       lists.
-</para>
+     </para>
 
      <para>
       Only persistent base tables and partitioned tables can be part of a