From 117f9f328e0f146a4b6de517501f4d5d994040a9 Mon Sep 17 00:00:00 2001 From: Amit Kapila Date: Fri, 24 Jan 2025 08:11:29 +0530 Subject: [PATCH] Doc: Fix column name in pg_publication catalog. Commit e65dbc9927 incorrectly spelled the column name in the pg_publication catalog. In passing make the order of columns in the doc match the actual catalog. Author: Shinoda, Noriyoshi Reviewed-by: Peter Smith Discussion: https://postgr.es/m/DM4PR84MB1734F8F140E4477580761F93EEE02@DM4PR84MB1734.NAMPRD84.PROD.OUTLOOK.COM --- doc/src/sgml/catalogs.sgml | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index c88bcaa7df9..8ad0ed10b3a 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -6396,26 +6396,26 @@ SCRAM-SHA-256$<iteration count>:&l - pubgencols char + pubviaroot bool - Controls how to handle generated column replication when there is no - publication column list: - n = generated columns in the tables associated with - the publication should not be replicated, - s = stored generated columns in the tables associated - with the publication should be replicated. + If true, operations on a leaf partition are replicated using the + identity and schema of its topmost partitioned ancestor mentioned in the + publication instead of its own. - pubviaroot bool + pubgencols_type char - If true, operations on a leaf partition are replicated using the - identity and schema of its topmost partitioned ancestor mentioned in the - publication instead of its own. + Controls how to handle generated column replication when there is no + publication column list: + n = generated columns in the tables associated with + the publication should not be replicated, + s = stored generated columns in the tables associated + with the publication should be replicated. -- 2.30.2