initdb -A trust -D /data/pg140 -E utf8 -k -U postgres -W --wal-segsize=10
24
user:postgres@db:postgres[[local]:5432]#select * from pg_stat_replication ;
+-[ RECORD 1 ]-----+-------------------------------+
| pid | 15236 |
| usesysid | 16384 |
| usename | replic |
| application_name | walreceiver |
| client_addr | 192.168.229.121 |
| client_hostname | NULL |
| client_port | 46028 |
| backend_start | 2021-08-11 10:30:16.978079+08 |
| backend_xmin | 499 |
| state | streaming |
| sent_lsn | 3/800000D8 |
| write_lsn | 3/800000D8 |
| flush_lsn | 3/800000D8 |
| replay_lsn | 3/800000D8 |
| write_lag | NULL |
| flush_lag | NULL |
| replay_lag | NULL |
| sync_priority | 0 |
| sync_state | async |
| reply_time | 2021-08-11 10:31:47.648992+08 |
+------------------+-------------------------------+
pg_ctl stop -D $PGDATA
[postgres@PG-1 pg133]$ /opt/pgsql/pg140/bin/pg_upgrade -b /opt/pgsql/pg133/bin/ -B /opt/pgsql/pg140/bin/ -d /data/pg133 -D /data/pg140 -j 8 -p 5432 -P 5433 -c
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
Checking database user is the install user ok
Checking database connection settings ok
Checking for prepared transactions ok
Checking for system-defined composite types in user tables ok
Checking for reg* data types in user tables ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking for user-defined encoding conversions ok
Checking for user-defined postfix operators ok
Checking for presence of required libraries ok
Checking database user is the install user ok
Checking for prepared transactions ok
Checking for new cluster tablespace directories ok
*Clusters are compatible*
[postgres@PG-1 pg133]$ /opt/pgsql/pg140/bin/pg_upgrade -b /opt/pgsql/pg133/bin/ -B /opt/pgsql/pg140/bin/ -d /data/pg133 -D /data/pg140 -j 8 -p 5432 -P 5433
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
Checking database user is the install user ok
Checking database connection settings ok
Checking for prepared transactions ok
Checking for system-defined composite types in user tables ok
Checking for reg* data types in user tables ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking for user-defined encoding conversions ok
Checking for user-defined postfix operators ok
Creating dump of global objects ok
Creating dump of database schemas
ok
Checking for presence of required libraries ok
Checking database user is the install user ok
Checking for prepared transactions ok
Checking for new cluster tablespace directories ok
If pg_upgrade fails after this point, you must re-initdb the
new cluster before continuing.
Performing Upgrade
------------------
Analyzing all rows in the new cluster ok
Freezing all rows in the new cluster ok
Deleting files from new pg_xact ok
Copying old pg_xact to new server ok
Setting next transaction ID and epoch for new cluster
ok
Deleting files from new pg_multixact/offsets ok
Copying old pg_multixact/offsets to new server ok
Deleting files from new pg_multixact/members ok
Copying old pg_multixact/members to new server ok
Setting next multixact ID and offset for new cluster ok
Resetting WAL archives ok
Setting frozenxid and minmxid counters in new cluster ok
Restoring global objects in the new cluster ok
Restoring database schemas in the new cluster
ok
Copying user relation files
ok
Setting next OID for new cluster ok
Sync data directory to disk ok
Creating script to delete old cluster ok
Upgrade Complete
----------------
Optimizer statistics are not transferred by pg_upgrade.
Once you start the new server, consider running:
/opt/pgsql/pg140/bin/vacuumdb --all --analyze-in-stages
Running this script will delete the old clusters data files:
./delete_old_cluster.sh
/opt/pgsql/pg140/bin/pg_ctl start -D /data/pg140
/opt/pgsql/pg140/bin/vacuumdb --all --analyze-in-stages
rsync -avz postgres@192.168.229.129:/data/pg140 /data
6. 启动standby数据库。
user:postgres@db:postgres[[local]:5432]#select * from pg_stat_replication;
+-[ RECORD 1 ]-----+-------------------------------+
| pid | 15980 |
| usesysid | 16384 |
| usename | replic |
| application_name | walreceiver |
| client_addr | 192.168.229.121 |
| client_hostname | NULL |
| client_port | 46122 |
| backend_start | 2021-08-11 11:23:38.478461+08 |
| backend_xmin | NULL |
| state | streaming |
| sent_lsn | 5/2ABF20 |
| write_lsn | 5/2ABF20 |
| flush_lsn | 5/2ABF20 |
| replay_lsn | 5/2ABF20 |
| write_lag | 00:00:00.000595 |
| flush_lag | 00:00:00.000982 |
| replay_lag | 00:00:00.001227 |
| sync_priority | 0 |
| sync_state | async |
| reply_time | 2021-08-11 11:23:51.450434+08 |
+------------------+-------------------------------+
文章版权归作者所有,未经允许请勿转载,若此文章存在违规行为,您可以联系管理员删除。
转载请注明本文地址:https://www.ucloud.cn/yun/129294.html
摘要:经过对比选型,用户同时选用三种数据库来针对性的满足不同目标。基于能够带来的这些特性优势,用户选择了。相比自建,其可靠性更高,方便运维维护。整个过程中用户不需要任何人工干预和配置修改,真正做到自动容灾。 据DB-Engines 最新发布的2019年8月份数据库流行度排行榜(如下图)显示,名列前茅的MySQL和PostgreSQL数据库的流行趋势与去年同期相比依然稳增不减。 showImg...
摘要:相比自建,其可靠性更高,方便运维维护。宋体经过审慎考虑,用户同时选用三种数据库,针对性的满足不同目标。宋体宋体其中,相比于在上的快速高效是其优势,也是用户选型的重要砝码。PostgreSQL UDB用在大数据分析上,查询效率更高。相比自建,其可靠性更高,方便运维维护。 — 31会议运维经理 汤雷 如何用好PostgreSQL? PostgreSQL是业内一款十分流行的开源数...
阅读 1249·2023-01-11 13:20
阅读 1558·2023-01-11 13:20
阅读 1012·2023-01-11 13:20
阅读 1680·2023-01-11 13:20
阅读 3971·2023-01-11 13:20
阅读 2519·2023-01-11 13:20
阅读 1355·2023-01-11 13:20
阅读 3486·2023-01-11 13:20