diff --git a/content/en/docs/Toolreference/command-reference.md b/content/en/docs/Toolreference/command-reference.md index 81a67b5e8e22bb9adc267096caa5a19f3557a93f..e21e60ce7384e35e2fa931a7ab2cc94d1f80e5ed 100644 --- a/content/en/docs/Toolreference/command-reference.md +++ b/content/en/docs/Toolreference/command-reference.md @@ -315,7 +315,7 @@ For details about **gsql** parameters, see [Table 1](#en-us_topic_0237152145_

Specifies the port number of the database server.

You can modify the default port number using the -p, --port=PORT parameter.

-

The default value is 8000.

+

The default value is 15400.

-U, --username=USERNAME

@@ -341,3 +341,4 @@ For details about **gsql** parameters, see [Table 1](#en-us_topic_0237152145_ + diff --git a/content/en/docs/Toolreference/faqs.md b/content/en/docs/Toolreference/faqs.md index bd6a5c1575c34f8c8531adc48eae99e01bbe6534..21e88f5782252dc51481bb2162ddbd29bec63b34 100644 --- a/content/en/docs/Toolreference/faqs.md +++ b/content/en/docs/Toolreference/faqs.md @@ -105,7 +105,7 @@ 1. Connect to the database as the system administrator **dbadmin**. ``` - gsql -d postgres -U dbadmin -p 8000 + gsql -d postgres -U dbadmin -p 15400 ``` 2. Grant the user with the permission to access the database. @@ -115,9 +115,9 @@ >![](public_sys-resources/icon-note.gif) **NOTE:** >Actually, some common misoperations may also cause a database connection failure, for example, entering an incorrect database name, username, or password. Misoperations are accompanied with an error information on the client tool. >``` - >gsql -d postgres -p 8000 + >gsql -d postgres -p 15400 >gsql: FATAL: database "postgres" does not exist - >gsql -d postgres -U user1 -W gauss@789 -p 8000 + >gsql -d postgres -U user1 -W gauss@789 -p 15400 >gsql: FATAL: Invalid username/password,login denied. >``` diff --git a/content/en/docs/Toolreference/gaussdb.md b/content/en/docs/Toolreference/gaussdb.md index f6b48c61f52257f35a447a426dbf8822a5a87081..3e025f57f6a2ac8a6264226b7974c6a7b9a0efec 100644 --- a/content/en/docs/Toolreference/gaussdb.md +++ b/content/en/docs/Toolreference/gaussdb.md @@ -155,7 +155,7 @@ The **gaussdb** command can also be called in single-user mode. The primary us

-p PORT

-

Specifies the TCP/IP port or local Unix domain socket file extension on which gaussdb is to listen for connections from client applications. The default port ID is 5432.

+

Specifies the TCP/IP port or local Unix domain socket file extension on which gaussdb is to listen for connections from client applications. The default port ID is 15400.

A positive integer within the port range supported by the OS.

@@ -212,6 +212,7 @@ The **gaussdb** command can also be called in single-user mode. The primary us + Parameters described in [Table 2](#en-us_topic_0237152404_en-us_topic_0059777816_en-us_topic_0058968126_table56695537) are used for debugging purposes, and in some cases for assisting in recovering severely damaged databases. Do not use these parameters for debugging if databases are providing services for applications. **Table 2** Developer options diff --git a/content/en/docs/Toolreference/gs_restore.md b/content/en/docs/Toolreference/gs_restore.md index b78a6721c34fe9375e8f4c6b79575e46b66146fd..42619b267da3b852fb64776daffa9c05764ea37e 100644 --- a/content/en/docs/Toolreference/gs_restore.md +++ b/content/en/docs/Toolreference/gs_restore.md @@ -246,7 +246,7 @@ Parameters for importing data >- If any local additions need to be added to the template1 database during the installation, restore the output of **gs\_restore** into an empty database with caution. Otherwise, you are likely to obtain errors due to duplicate definitions of the added objects. To create an empty database without any local additions, copy data from template0 rather than template1. Example: >``` >CREATE DATABASE foo WITH TEMPLATE template0; ->``` +>``` >- **gs\_restore** cannot import large objects selectively. For example, it can only import the objects of a specified table. If an archive contains large objects, all large objects will be imported, or none of them will be restored if they are excluded by using **-L**, **-t**, or other parameters. >![](public_sys-resources/icon-note.gif) **NOTE:** @@ -324,7 +324,7 @@ total time: 30476 ms Example 1: Execute the **gs\_restore** tool to import the exported **MPPDB\_backup.dmp** file \(custom format\) to the **postgres** database. ``` -gs_restore -W Bigdata@123 backup/MPPDB_backup.dmp -p 5432 -d postgres +gs_restore -W Bigdata@123 backup/MPPDB_backup.dmp -p 15400 -d postgres gs_restore: restore operation successful gs_restore: total time: 13053 ms ``` @@ -332,7 +332,7 @@ gs_restore: total time: 13053 ms Example 2: Execute the **gs\_restore** tool to import the exported **MPPDB\_backup.tar** file \(.tar format\) to the **postgres** database. ``` -gs_restore backup/MPPDB_backup.tar -p 5432 -d postgres +gs_restore backup/MPPDB_backup.tar -p 15400 -d postgres gs_restore[2017-07-21 19:16:26]: restore operation successful gs_restore[2017-07-21 19:16:26]: total time: 21203 ms ``` @@ -340,7 +340,7 @@ gs_restore[2017-07-21 19:16:26]: total time: 21203 ms Example 3: Execute the **gs\_restore** tool to import the exported **MPPDB\_backup** file \(directory format\) to the **postgres** database. ``` -gs_restore backup/MPPDB_backup -p 5432 -d postgres +gs_restore backup/MPPDB_backup -p 15400 -d postgres gs_restore[2017-07-21 19:16:26]: restore operation successful gs_restore[2017-07-21 19:16:26]: total time: 21003 ms ``` @@ -348,7 +348,7 @@ gs_restore[2017-07-21 19:16:26]: total time: 21003 ms Example 4: Execute the **gs\_restore** tool and run the following commands to import the **MPPDB\_backup.dmp** file \(in custom format\). Specifically, import all the object definitions and data in the **PUBLIC** schema. Existing objects are deleted from the target database before the import. If an existing object references to an object in another schema, you need to manually delete the referenced object first. ``` -gs_restore backup/MPPDB_backup.dmp -p 5432 -d postgres -e -c -n PUBLIC +gs_restore backup/MPPDB_backup.dmp -p 15400 -d postgres -e -c -n PUBLIC gs_restore: [archiver (db)] Error while PROCESSING TOC: gs_restore: [archiver (db)] Error from TOC entry 313; 1259 337399 TABLE table1 gaussdba gs_restore: [archiver (db)] could not execute query: ERROR: cannot drop table table1 because other objects depend on it @@ -360,7 +360,7 @@ HINT: Use DROP ... CASCADE to drop the dependent objects too. Manually delete the referenced object and create it again after the import is complete. ``` -gs_restore backup/MPPDB_backup.dmp -p 5432 -d postgres -e -c -n PUBLIC +gs_restore backup/MPPDB_backup.dmp -p 15400 -d postgres -e -c -n PUBLIC gs_restore[2017-07-21 19:16:26]: restore operation successful gs_restore[2017-07-21 19:16:26]: total time: 2203 ms ``` @@ -368,7 +368,7 @@ gs_restore[2017-07-21 19:16:26]: total time: 2203 ms Example 5: Execute the **gs\_restore** tool and run the following commands to import the **MPPDB\_backup.dmp** file \(in custom format\). Specifically, import only the definition of **table1** in the **PUBLIC** schema. ``` -gs_restore backup/MPPDB_backup.dmp -p 5432 -d postgres -e -c -s -n PUBLIC -t table1 +gs_restore backup/MPPDB_backup.dmp -p 15400 -d postgres -e -c -s -n PUBLIC -t table1 gs_restore[2017-07-21 19:16:26]: restore operation successful gs_restore[2017-07-21 19:16:26]: total time: 21000 ms ``` @@ -376,7 +376,7 @@ gs_restore[2017-07-21 19:16:26]: total time: 21000 ms Example 6: Execute the **gs\_restore** tool and run the following commands to import the **MPPDB\_backup.dmp** file \(in custom format\). Specifically, import only the data of **table1** in the **PUBLIC** schema. ``` -gs_restore backup/MPPDB_backup.dmp -p 5432 -d postgres -e -a -n PUBLIC -t table1 +gs_restore backup/MPPDB_backup.dmp -p 15400 -d postgres -e -a -n PUBLIC -t table1 gs_restore[2017-07-21 19:16:26]: restore operation successful gs_restore[2017-07-21 19:16:26]: total time: 20203 ms ``` diff --git a/content/en/docs/Toolreference/obtaining-help-information.md b/content/en/docs/Toolreference/obtaining-help-information.md index 27ba002883c43c13f68c50c263409a421849e52f..cd83472e5746041653e4e543d77439036ba2bdc0 100644 --- a/content/en/docs/Toolreference/obtaining-help-information.md +++ b/content/en/docs/Toolreference/obtaining-help-information.md @@ -45,10 +45,10 @@ 1. Run the following command to connect to the database: ``` - gsql -d postgres -p 8000 + gsql -d postgres -p 15400 ``` - **postgres** is the name of the database, and **8000** is the port number of the CN. + **postgres** is the name of the database, and **15400** is the port number of the CN. If information similar to the following is displayed, the connection succeeds: diff --git a/content/en/docs/Toolreference/usage-guidelines.md b/content/en/docs/Toolreference/usage-guidelines.md index 09bec9e29fad259cfa8712f800d95a3b4127241d..c039216fa98edc426353b86092c7f88d89a1c1f9 100644 --- a/content/en/docs/Toolreference/usage-guidelines.md +++ b/content/en/docs/Toolreference/usage-guidelines.md @@ -17,28 +17,28 @@ You can use the **gsql** command to connect to the local database service or r >![](public_sys-resources/icon-note.gif) **NOTE:** >If the database name is not specified, the default database name generated during initialization will be used. If the database username is not specified, the current OS username will be used by default. If a variable does not belong to any parameter \(such as **-d** and **-U**\), and **-d** is not specified, the variable will be used as the database name. If **-d** is specified but **-U** is not specified, the variable will be used as the database username. - Example 1: Connect to the 8000 port of the local postgres database as user **omm**. + Example 1: Connect to the 15400 port of the local postgres database as user **omm**. ``` - gsql -d postgres -p 8000 + gsql -d postgres -p 15400 ``` - Example 2: Connect to the 8000 port of the remote postgres database as user **jack**. + Example 2: Connect to the 15400 port of the remote postgres database as user **jack**. ``` - gsql -h 10.180.123.163 -d postgres -U jack -p 8000 + gsql -h 10.180.123.163 -d postgres -U jack -p 15400 ``` Example 3: _postgres_ and _omm_ do not belong to any parameter, and they are used as the database name and the username, respectively. ``` - gsql postgres omm -p 8000 + gsql postgres omm -p 15400 ``` **Equals** ``` - gsql -d postgres -U omm -p 8000 + gsql -d postgres -U omm -p 15400 ``` For details about the **gsql** parameters, see [Command Reference](en-us_topic_0237152145.md). diff --git a/content/en/docs/installation/(optional)-setting-the-standby-node-to-readable.md b/content/en/docs/installation/(optional)-setting-the-standby-node-to-readable.md index 3d35436089129dd915d0436e844cb10053c70d49..6cf8b21e959373a5907b1049660b401e2d5481b9 100644 --- a/content/en/docs/installation/(optional)-setting-the-standby-node-to-readable.md +++ b/content/en/docs/installation/(optional)-setting-the-standby-node-to-readable.md @@ -5,6 +5,6 @@ Readable standby node is an optional feature. You need to modify the configurati ## Procedure 1. If the openGauss database instance is running on the primary and standby nodes, stop the database instance on both nodes. -2. Open the **postgres.conf** configuration files of the primary and standby nodes based on the corresponding paths in [Table 2](configuring-primary-database-node-information.md#en-us_topic_0241802596_table15838192510429), find the corresponding parameters, and change the parameter values to **wal\_level=hot\_standby**, **hot\_standby = on**, and **hot\_standby\_feedback = on**. +2. Open the **postgres.conf** configuration files of the primary and standby nodes based on the corresponding paths in [Table 2](configuring-primary-database-node-information.md#en-us_topic_0241802596_table15838192510429), find the corresponding parameters, and change the parameter values to **wal\_level=hot\_standby**, **hot\_standby = on**, and **hot\_standby\_feedback = on**. 3. After the modification, start the primary and standby nodes. diff --git a/content/en/docs/installation/configuring-primary-database-node-information.md b/content/en/docs/installation/configuring-primary-database-node-information.md index bc0720512570f1113ec1d45f2108e61dcb0efdb8..6e5d5a6733578d43bff42f5b07a5111a0a0ef103 100644 --- a/content/en/docs/installation/configuring-primary-database-node-information.md +++ b/content/en/docs/installation/configuring-primary-database-node-information.md @@ -81,9 +81,10 @@ The information in bold is only an example. You can replace it as required. Each

Standby database node

/opt/huawei/install/data/slaveX

-

xxx indicates the name of the current standby database node.

+

slaveX indicates the name of the current standby database node.

+ diff --git a/content/zh/docs/Toolreference/gaussdb.md b/content/zh/docs/Toolreference/gaussdb.md index c19ebe564a3a81ff6a53536ecf652c64b55b3404..264f5fe748d53afe89c124d6869fbb83a2b09470 100644 --- a/content/zh/docs/Toolreference/gaussdb.md +++ b/content/zh/docs/Toolreference/gaussdb.md @@ -155,7 +155,7 @@ gaussdb接受[表1](#zh-cn_topic_0237152404_zh-cn_topic_0059777816_zh-cn_topic_0

-p PORT

-

指定gaussdb侦听客户端连接的TCP/IP端口或本地Unix domain socket文件的扩展。默认端口号为5432。

+

指定gaussdb侦听客户端连接的TCP/IP端口或本地Unix domain socket文件的扩展。默认端口号为15400。

正整数，在操作系统支持的端口范围内。

diff --git a/content/zh/docs/Toolreference/gs_restore.md b/content/zh/docs/Toolreference/gs_restore.md index ce219820e633244e417e8143622fd7ab6d509ae0..456626c3f45862f6933d9b5ac2c2ccf9ae62e1cf 100644 --- a/content/zh/docs/Toolreference/gs_restore.md +++ b/content/zh/docs/Toolreference/gs_restore.md @@ -246,7 +246,7 @@ gs_restore [OPTION]... FILE >- 如果安装过程中有任何本地数据要添加到template1数据库，请谨慎将gs\_restore的输出载入到一个真正的空数据库中；否则可能会因为被添加对象的定义被复制，而出现错误。要创建一个无本地添加的空数据库，需从template0而非template1复制，例如： >``` >CREATE DATABASE foo WITH TEMPLATE template0; ->``` +>``` >- gs\_restore不能选择性地导入大对象；例如只能导入那些指定表的对象。如果某个归档形式包含大对象，那所有大对象都会被导入，或一个都不会被导入，如果它们通过-L、-t或其他选项被排除。 >![](public_sys-resources/icon-note.gif) **说明：** @@ -296,7 +296,7 @@ gs_restore [OPTION]... FILE 特例：执行gsql程序，使用如下选项导入由gs\_dump/gs\_dumpall生成导出文件夹（纯文本格式）的MPPDB\_backup.sql文件到postgres数据库。 ``` -gsql -d postgres -p 5432 -W Bigdata@123 -f /home/omm/test/MPPDB_backup.sql +gsql -d postgres -p 15400 -W Bigdata@123 -f /home/omm/test/MPPDB_backup.sql SET SET SET @@ -324,7 +324,7 @@ gs\_restore用来导入由gs\_dump生成的导出文件。 示例1：执行gs\_restore，将导出的MPPDB\_backup.dmp文件（自定义归档格式）导入到postgres数据库。 ``` -gs_restore -W Bigdata@123 backup/MPPDB_backup.dmp -p 5432 -d postgres +gs_restore -W Bigdata@123 backup/MPPDB_backup.dmp -p 15400 -d postgres gs_restore: restore operation successful gs_restore: total time: 13053 ms ``` @@ -332,7 +332,7 @@ gs_restore: total time: 13053 ms 示例2：执行gs\_restore，将导出的MPPDB\_backup.tar文件（tar格式）导入到postgres数据库。 ``` -gs_restore backup/MPPDB_backup.tar -p 5432 -d postgres +gs_restore backup/MPPDB_backup.tar -p 15400 -d postgres gs_restore[2017-07-21 19:16:26]: restore operation successful gs_restore[2017-07-21 19:16:26]: total time: 21203 ms ``` @@ -340,7 +340,7 @@ gs_restore[2017-07-21 19:16:26]: total time: 21203 ms 示例3：执行gs\_restore，将导出的MPPDB\_backup文件（目录格式）导入到postgres数据库。 ``` -gs_restore backup/MPPDB_backup -p 5432 -d postgres +gs_restore backup/MPPDB_backup -p 15400 -d postgres gs_restore[2017-07-21 19:16:26]: restore operation successful gs_restore[2017-07-21 19:16:26]: total time: 21003 ms ``` @@ -348,7 +348,7 @@ gs_restore[2017-07-21 19:16:26]: total time: 21003 ms 示例4：执行gs\_restore，使用自定义归档格式的MPPDB\_backup.dmp文件来进行如下导入操作。 导入PUBLIC模式下所有对象的定义和数据。在导入时会先删除已经存在的对象，如果原对象存在跨模式的依赖则需手工强制干预。 ``` -gs_restore backup/MPPDB_backup.dmp -p 5432 -d postgres -e -c -n PUBLIC +gs_restore backup/MPPDB_backup.dmp -p 15400 -d postgres -e -c -n PUBLIC gs_restore: [archiver (db)] Error while PROCESSING TOC: gs_restore: [archiver (db)] Error from TOC entry 313; 1259 337399 TABLE table1 gaussdba gs_restore: [archiver (db)] could not execute query: ERROR: cannot drop table table1 because other objects depend on it @@ -360,7 +360,7 @@ HINT: Use DROP ... CASCADE to drop the dependent objects too. 手工删除依赖，导入完成后再重新创建。 ``` -gs_restore backup/MPPDB_backup.dmp -p 5432 -d postgres -e -c -n PUBLIC +gs_restore backup/MPPDB_backup.dmp -p 15400 -d postgres -e -c -n PUBLIC gs_restore[2017-07-21 19:16:26]: restore operation successful gs_restore[2017-07-21 19:16:26]: total time: 2203 ms ``` @@ -368,7 +368,7 @@ gs_restore[2017-07-21 19:16:26]: total time: 2203 ms 示例5：执行gs\_restore，使用自定义归档格式的MPPDB\_backup.dmp文件来进行如下导入操作。只导入PUBLIC模式下表table1的定义。 ``` -gs_restore backup/MPPDB_backup.dmp -p 5432 -d postgres -e -c -s -n PUBLIC -t table1 +gs_restore backup/MPPDB_backup.dmp -p 15400 -d postgres -e -c -s -n PUBLIC -t table1 gs_restore[2017-07-21 19:16:26]: restore operation successful gs_restore[2017-07-21 19:16:26]: total time: 21000 ms ``` @@ -376,7 +376,7 @@ gs_restore[2017-07-21 19:16:26]: total time: 21000 ms 示例6：执行gs\_restore，使用自定义归档格式的MPPDB\_backup.dmp文件来进行如下导入操作。只导入PUBLIC模式下表table1的数据。 ``` -gs_restore backup/MPPDB_backup.dmp -p 5432 -d postgres -e -a -n PUBLIC -t table1 +gs_restore backup/MPPDB_backup.dmp -p 15400 -d postgres -e -a -n PUBLIC -t table1 gs_restore[2017-07-21 19:16:26]: restore operation successful gs_restore[2017-07-21 19:16:26]: total time: 20203 ms ``` diff --git "a/content/zh/docs/Toolreference/\344\275\277\347\224\250\346\214\207\345\257\274.md" "b/content/zh/docs/Toolreference/\344\275\277\347\224\250\346\214\207\345\257\274.md" index 69ee2da12101982b97f0f57aa8881832efdc611a..fd1c445c45b60a0e5f4b0bdc10f17879cbe262c3 100644 --- "a/content/zh/docs/Toolreference/\344\275\277\347\224\250\346\214\207\345\257\274.md" +++ "b/content/zh/docs/Toolreference/\344\275\277\347\224\250\346\214\207\345\257\274.md" @@ -17,28 +17,28 @@ >![](public_sys-resources/icon-note.gif) **说明：** >若未指定数据库名称，则使用初始化时默认生成的数据库名称；若未指定数据库用户名，则默认使用当前操作系统用户作为数据库用户名；当某个值没有前面的参数（-d、-U等）时，若连接的命令中没有指定数据库名（-d）则该参数会被解释成数据库名；如果已经指定数据库名（-d）而没有指定数据库用户名（-U）时，该参数则会被解释成数据库用户名。 - 示例1，使用omm用户连接到本机postgres数据库的5432端口。 + 示例1，使用omm用户连接到本机postgres数据库的15400端口。 ``` - gsql -d postgres -p 5432 + gsql -d postgres -p 15400 ``` - 示例2，使用jack用户连接到远程主机postgres数据库的5432端口。 + 示例2，使用jack用户连接到远程主机postgres数据库的15400端口。 ``` - gsql -h 10.180.123.163 -d postgres -U jack -p 5432 + gsql -h 10.180.123.163 -d postgres -U jack -p 15400 ``` 示例3，参数postgres和omm不属于任何选项时，分别被解释成了数据库名和用户名。 ``` - gsql postgres omm -p 5432 + gsql postgres omm -p 15400 ``` **等效于** ``` - gsql -d postgres -U omm -p 5432 + gsql -d postgres -U omm -p 15400 ``` 详细的gsql参数请参见[命令参考](命令参考.md)。 diff --git "a/content/zh/docs/Toolreference/\345\221\275\344\273\244\345\217\202\350\200\203.md" "b/content/zh/docs/Toolreference/\345\221\275\344\273\244\345\217\202\350\200\203.md" index f0e21362f488a5d0212da5fec92d68defb9f7c7b..57f2f913c2063d8c887965a57446ba7ebf3f646e 100644 --- "a/content/zh/docs/Toolreference/\345\221\275\344\273\244\345\217\202\350\200\203.md" +++ "b/content/zh/docs/Toolreference/\345\221\275\344\273\244\345\217\202\350\200\203.md" @@ -311,7 +311,7 @@

指定数据库服务器的端口号。

可以通过port参数修改默认端口号。

-

默认为5432。

+

默认为15400。

-U, --username=USERNAME

@@ -337,3 +337,4 @@ + diff --git "a/content/zh/docs/Toolreference/\345\270\270\350\247\201\351\227\256\351\242\230\345\244\204\347\220\206.md" "b/content/zh/docs/Toolreference/\345\270\270\350\247\201\351\227\256\351\242\230\345\244\204\347\220\206.md" index 7a8268e7ccf48f9edb03a72f05fe1e4087f5aff6..bbc378e721a428d9c65a1f28be96ce5128641120 100644 --- "a/content/zh/docs/Toolreference/\345\270\270\350\247\201\351\227\256\351\242\230\345\244\204\347\220\206.md" +++ "b/content/zh/docs/Toolreference/\345\270\270\350\247\201\351\227\256\351\242\230\345\244\204\347\220\206.md" @@ -97,7 +97,7 @@ 1. 使用管理员用户dbadmin连接数据库。 ``` - gsql -d postgres -U dbadmin -p 5432 + gsql -d postgres -U dbadmin -p 15400 ``` 2. 赋予该用户访问数据库的权限。 @@ -107,9 +107,9 @@ >![](public_sys-resources/icon-note.gif) **说明：** >实际上，常见的许多错误操作也可能产生用户无法连接上数据库的现象。如用户连接的数据库不存在，用户名或密码输入错误等。这些错误操作在客户端工具也有相应的提示信息。 >``` - >gsql -d postgres -p 5432 + >gsql -d postgres -p 15400 >gsql: FATAL: database "postgres" does not exist - >gsql -d postgres -U user1 -W gauss@789 -p 5432 + >gsql -d postgres -U user1 -W gauss@789 -p 15400 >gsql: FATAL: Invalid username/password,login denied. >``` diff --git "a/content/zh/docs/Toolreference/\350\216\267\345\217\226\345\270\256\345\212\251.md" "b/content/zh/docs/Toolreference/\350\216\267\345\217\226\345\270\256\345\212\251.md" index 8d54e34a9048a6e3a59854a048e8c78388e4eff7..0f2fb830c31fe40ff27a7cf1bd55f0fd9749ddb9 100644 --- "a/content/zh/docs/Toolreference/\350\216\267\345\217\226\345\270\256\345\212\251.md" +++ "b/content/zh/docs/Toolreference/\350\216\267\345\217\226\345\270\256\345\212\251.md" @@ -45,10 +45,10 @@ 1. 使用如下命令连接数据库。 ``` - gsql -d postgres -p 5432 + gsql -d postgres -p 15400 ``` - postgres为需要连接的数据库名称，5432为数据库主节点的端口号。 + postgres为需要连接的数据库名称，15400为数据库主节点的端口号。 连接成功后，系统显示类似如下信息： diff --git "a/content/zh/docs/installation/\351\205\215\347\275\256\346\225\260\346\215\256\345\272\223\344\270\273\350\212\202\347\202\271\344\277\241\346\201\257.md" "b/content/zh/docs/installation/\351\205\215\347\275\256\346\225\260\346\215\256\345\272\223\344\270\273\350\212\202\347\202\271\344\277\241\346\201\257.md" index 017f58a8e669a87508a12d0249bea9f19611c78d..86a0d79521649a8a93c8515355b24eb97dea9ca3 100644 --- "a/content/zh/docs/installation/\351\205\215\347\275\256\346\225\260\346\215\256\345\272\223\344\270\273\350\212\202\347\202\271\344\277\241\346\201\257.md" +++ "b/content/zh/docs/installation/\351\205\215\347\275\256\346\225\260\346\215\256\345\272\223\344\270\273\350\212\202\347\202\271\344\277\241\346\201\257.md" @@ -81,9 +81,10 @@

备DBnode

/opt/huawei/install/data/slaveX

-

其中，xxx为当前备DBnode的名称。

+

其中，slaveX为当前备DBnode的名称。

+ diff --git "a/content/zh/docs/installation/\357\274\210\345\217\257\351\200\211\357\274\211\350\256\276\347\275\256\345\244\207\346\234\272\345\217\257\350\257\273.md" "b/content/zh/docs/installation/\357\274\210\345\217\257\351\200\211\357\274\211\350\256\276\347\275\256\345\244\207\346\234\272\345\217\257\350\257\273.md" index d6d93dbf439d3b8aff402deb1e1b9cb81123e9dc..cd1c4483ff848c235a5a6e793ac32a700047bcd1 100644 --- "a/content/zh/docs/installation/\357\274\210\345\217\257\351\200\211\357\274\211\350\256\276\347\275\256\345\244\207\346\234\272\345\217\257\350\257\273.md" +++ "b/content/zh/docs/installation/\357\274\210\345\217\257\351\200\211\357\274\211\350\256\276\347\275\256\345\244\207\346\234\272\345\217\257\350\257\273.md" @@ -5,6 +5,6 @@ ## 操作步骤 1. 如果主备机上的openGauss数据库实例正在运行，请先分别停止主备机上的数据库实例。 -2. 根据[表2](配置数据库主节点信息.md#zh-cn_topic_0241802596_table15838192510429)对应路径，分别打开主机与备机的postgres.conf配置文件，找到并将对应参数修改为：wal\_level=hot\_standby ; hot\_standby = on；hot\_standby\_feedback = on。 +2. 根据[表2](配置数据库主节点信息.md#zh-cn_topic_0241802596_table15838192510429)对应路径，分别打开主机与备机的postgres.conf配置文件，找到并将对应参数修改为：wal\_level=hot\_standby ；hot\_standby = on；hot\_standby\_feedback = on。 3. 修改完成后，分别启动主备机即可。