我要评论先自我介绍一下，小编浙江大学毕业，去过华为、字节跳动等大厂，目前阿里p7
深知大多数程序员，想要提升技能，往往是自己摸索成长，但自己不成体系的自学效果低效又漫长，而且极易碰到天花板技术停滞不前！
因此收集整理了一份《2024年最新软件测试全套学习资料》，初衷也很简单，就是希望能够帮助到想自学提升又不知道该从何学起的朋友。
既有适合小白学习的零基础资料，也有适合3年以上经验的小伙伴深入学习提升的进阶课程，涵盖了95%以上软件测试知识点，真正体系化！
由于文件比较多，这里只是将部分目录截图出来，全套包含大厂面经、学习笔记、源码讲义、实战项目、大纲路线、讲解视频，并且后续会持续更新
如果你需要这些资料，可以添加v获取：vip1024b （备注软件测试）
正文
up broadcast running multicast mtu:1500 metric:1
rx packets:141173 errors:0 dropped:0 overruns:0 frame:0
tx packets:29124 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
rx bytes:198747523 (189.5 mib) tx bytes:2168654 (2.0 mib)
lo link encap:local loopback
inet addr:127.0.0.1 mask:255.0.0.0
inet6 addr: ::1/128 scope:host
up loopback running mtu:16436 metric:1
rx packets:636 errors:0 dropped:0 overruns:0 frame:0
tx packets:636 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
rx bytes:139280 (136.0 kib) tx bytes:139280 (136.0 kib)
利用ip地址漂移实现主备切换
切换前观察ip地址情况和数据库的主备情况
ip地址：主端
[root@node1 ~]# ifconfig
eth0 link encap:ethernet hwaddr 00:0c:29:ea:af:6e
inet addr:192.168.11.68 bcast:192.168.11.255 mask:255.255.255.0
inet6 addr: fe80::20c:29ff:feea:af6e/64 scope:link
up broadcast running multicast mtu:1500 metric:1
rx packets:29953 errors:0 dropped:0 overruns:0 frame:0
tx packets:141299 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
rx bytes:2174739 (2.0 mib) tx bytes:198989432 (189.7 mib)
eth0:1 link encap:ethernet hwaddr 00:0c:29:ea:af:6e
inet addr:192.168.11.40 bcast:192.168.11.255 mask:255.255.255.0
up broadcast running multicast mtu:1500 metric:1
lo link encap:local loopback
inet addr:127.0.0.1 mask:255.0.0.0
inet6 addr: ::1/128 scope:host
up loopback running mtu:16436 metric:1
rx packets:308 errors:0 dropped:0 overruns:0 frame:0
tx packets:308 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
rx bytes:55374 (54.0 kib) tx bytes:55374 (54.0 kib)
备端
[root@node2 ~]# ifconfig
eth0 link encap:ethernet hwaddr 00:0c:29:ea:af:6e
inet addr:192.168.11.70 bcast:192.168.11.255 mask:255.255.255.0
inet6 addr: fe80::20c:29ff:feea:af6e/64 scope:link
up broadcast running multicast mtu:1500 metric:1
rx packets:29953 errors:0 dropped:0 overruns:0 frame:0
tx packets:141299 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
rx bytes:2174739 (2.0 mib) tx bytes:198989432 (189.7 mib)
lo link encap:local loopback
inet addr:127.0.0.1 mask:255.0.0.0
inet6 addr: ::1/128 scope:host
up loopback running mtu:16436 metric:1
rx packets:308 errors:0 dropped:0 overruns:0 frame:0
tx packets:308 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
rx bytes:55374 (54.0 kib) tx bytes:55374 (54.0 kib)
数据库情况
主端
[postgres@node1 ~]$ pg_controldata
pg_control version number: 922
catalog version number: 201204301
database system identifier: 6377220794669856238
database cluster state:
in production
pg_control last modified: mon 23 jan 2017 09:13:29 am cst
latest checkpoint location: 0/12015cd0
prior checkpoint location: 0/12015c70
latest checkpoint’s redo location: 0/12015cd0
latest checkpoint’s timelineid: 2
latest checkpoint’s full_page_writes: on
latest checkpoint’s nextxid: 0/1822
latest checkpoint’s nextoid: 16397
latest checkpoint’s nextmultixactid: 1
latest checkpoint’s nextmultioffset: 0
latest checkpoint’s oldestxid: 1802
latest checkpoint’s oldestxid’s db: 1
latest checkpoint’s oldestactivexid: 0
time of latest checkpoint: mon 23 jan 2017 09:11:41 am cst
minimum recovery ending location: 0/0
backup start location: 0/0
backup end location: 0/0
end-of-backup record required: no
current wal_level setting: hot_standby
current max_connections setting: 100
current max_prepared_xacts setting: 0
current max_locks_per_xact setting: 64
maximum data alignment: 8
database block size: 8192
blocks per segment of large relation: 131072
wal block size: 8192
bytes per wal segment: 16777216
maximum length of identifiers: 64
maximum columns in an index: 32
maximum size of a toast chunk: 1996
date/time type storage: 64-bit integers
float4 argument passing: by value
float8 argument passing: by value
[postgres@node2 ~]$ pg_controldata
pg_control version number: 922
catalog version number: 201204301
database system identifier: 6377220794669856238
database cluster state:
in archive recovery
pg_control last modified: mon 23 jan 2017 09:13:09 am cst
latest checkpoint location: 0/12015d30
prior checkpoint location: 0/12015c10
latest checkpoint’s redo location: 0/12015d30
latest checkpoint’s timelineid: 3
latest checkpoint’s full_page_writes: on
latest checkpoint’s nextxid: 0/1822
latest checkpoint’s nextoid: 16397
latest checkpoint’s nextmultixactid: 1
latest checkpoint’s nextmultioffset: 0
latest checkpoint’s oldestxid: 1802
latest checkpoint’s oldestxid’s db: 1
latest checkpoint’s oldestactivexid: 0
time of latest checkpoint: mon 23 jan 2017 09:13:09 am cst
minimum recovery ending location: 0/0
backup start location: 0/0
backup end location: 0/0
end-of-backup record required: no
current wal_level setting: hot_standby
current max_connections setting: 100
current max_prepared_xacts setting: 0
current max_locks_per_xact setting: 64
maximum data alignment: 8
database block size: 8192
blocks per segment of large relation: 131072
wal block size: 8192
bytes per wal segment: 16777216
maximum length of identifiers: 64
maximum columns in an index: 32
maximum size of a toast chunk: 1996
date/time type storage: 64-bit integers
float4 argument passing: by value
float8 argument passing: by value
备端情况
首先，关闭主库
[postgres@node1 data]$ pg_ctl stop -m fast
[root@node1 ~]# ifdown eth0:1
[root@node1 ~]# ifconfig
eth0 link encap:ethernet hwaddr 00:0c:29:ea:af:6e
inet addr:192.168.11.68 bcast:192.168.11.255 mask:255.255.255.0
inet6 addr: fe80::20c:29ff:feea:af6e/64 scope:link
up broadcast running multicast mtu:1500 metric:1
rx packets:30248 errors:0 dropped:0 overruns:0 frame:0
tx packets:141525 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
rx bytes:2199137 (2.0 mib) tx bytes:199102358 (189.8 mib)
lo link encap:local loopback
inet addr:127.0.0.1 mask:255.0.0.0
inet6 addr: ::1/128 scope:host
up loopback running mtu:16436 metric:1
rx packets:348 errors:0 dropped:0 overruns:0 frame:0
tx packets:348 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
rx bytes:60247 (58.8 kib) tx bytes:60247 (58.8 kib)
备库
[root@node2 ~]# ifup eth0:1
active connection state: activating
active connection path: /org/freedesktop/networkmanager/activeconnection/1
state: activated
connection activated
[root@node2 ~]# ifconfig
eth0 link encap:ethernet hwaddr 00:0c:29:ea:af:6e
inet addr:192.168.11.70 bcast:192.168.11.255 mask:255.255.255.0
inet6 addr: fe80::20c:29ff:feea:af6e/64 scope:link
up broadcast running multicast mtu:1500 metric:1
rx packets:29953 errors:0 dropped:0 overruns:0 frame:0
tx packets:141299 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
rx bytes:2174739 (2.0 mib) tx bytes:198989432 (189.7 mib)
eth0:1 link encap:ethernet hwaddr 00:0c:29:ea:af:6e
inet addr:192.168.11.40 bcast:192.168.11.255 mask:255.255.255.0
up broadcast running multicast mtu:1500 metric:1
lo link encap:local loopback
inet addr:127.0.0.1 mask:255.0.0.0
inet6 addr: ::1/128 scope:host
up loopback running mtu:16436 metric:1
rx packets:308 errors:0 dropped:0 overruns:0 frame:0
tx packets:308 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
rx bytes:55374 (54.0 kib) tx bytes:55374 (54.0 kib)
备库进行切换
[postgres@node2 ~]$ pg_ctl promote
server promoting
原备库状态
[highgo@node2 ~]$ pg_controldata
pg_control version number: 922
catalog version number: 201204301
database system identifier: 6377220794669856238
database cluster state:
in production
pg_control last modified: mon 23 jan 2017 09:13:09 am cst
latest checkpoint location: 0/12015d30
prior checkpoint location: 0/12015c10
latest checkpoint’s redo location: 0/12015d30
latest checkpoint’s timelineid: 3
latest checkpoint’s full_page_writes: on
latest checkpoint’s nextxid: 0/1822
latest checkpoint’s nextoid: 16397
latest checkpoint’s nextmultixactid: 1
latest checkpoint’s nextmultioffset: 0
latest checkpoint’s oldestxid: 1802
latest checkpoint’s oldestxid’s db: 1
latest checkpoint’s oldestactivexid: 0
time of latest checkpoint: mon 23 jan 2017 09:13:09 am cst
minimum recovery ending location: 0/0
backup start location: 0/0
backup end location: 0/0
end-of-backup record required: no
current wal_level setting: hot_standby
current max_connections setting: 100
current max_prepared_xacts setting: 0
current max_locks_per_xact setting: 64
maximum data alignment: 8
database block size: 8192
blocks per segment of large relation: 131072
wal block size: 8192
bytes per wal segment: 16777216
maximum length of identifiers: 64
maximum columns in an index: 32
maximum size of a toast chunk: 1996
date/time type storage: 64-bit integers
float4 argument passing: by value
float8 argument passing: by value
[postgres@node2 ~]$ ps -ef | grep postgres
postgres 2538 1 0 09:11 pts/0 00:00:00 /opt/pgsql/bin/postgres
postgres 2539 2538 0 09:11 ? 00:00:00 postgres: logger process
postgres 2541 2538 0 09:11 ? 00:00:00 postgres: checkpointer process
postgres 2542 2538 0 09:11 ? 00:00:00 postgres: writer process
postgres 2543 2538 0 09:11 ? 00:00:00 postgres: stats collector process
postgres 2625 2538 0 09:13 ? 00:00:00
postgres: wal writer process
postgres 2626 2538 0 09:13 ? 00:00:00 postgres: autovacuum launcher process
postgres 2432 2425 0 09:06 ? 00:00:00 postgres: stats collector process
postgrs 2435 2425 0 09:06 ? 00:00:00
postgres: archiver process last was 000000.4history
root 3348 1992 0 10:06 pts/0 00:00:00 su - postgres
postgres 3349 3348 0 10:06 pts/0 00:00:00 -bash
postgres 3395 3349 0 10:13 pts/0 00:00:00 ps -ef
postgres 3396 3349 0 10:13 pts/0 00:00:00 grep postgres
在原主库配置recovery.conf文件
[postgres@node1 data]$ vi recovery.conf
standby_mode=‘on’
recovery_target_timeline = ‘latest’
primary_conninfo=‘host=192.168.11.68 port=5866 user=standby password=standby’
trigger_file=‘opt/pgsql/trigger_node’
启动原主库
[postgres@node2 ~]$ pg_ctl start
[postgres@node2 ~]$ ps -ef | grep postgres
postgres 2169 1 0 09:04 pts/0 00:00:00 /opt/pgsql/bin/postgres
postgres 2170 2169 0 09:04 ? 00:00:00 postgres: logger process
postgres 2171 2169 0 09:04 ? 00:00:00 postgres: startup process waiting for 000000020000000000000012
postgres 2172 2169 0 09:04 ? 00:00:00 postgres: checkpointer process
postgres 2173 2169 0 09:04 ? 00:00:00 postgres: writer process
postgres 2175 2169 0 09:04 ? 00:00:00 postgres: stats collector process
root 2241 1992 0 09:06 pts/0 00:00:00 su - postgres
postgres 2242 2241 0 09:06 pts/0 00:00:00 -bash
postgres 2283 2169 0 09:07 ? 00:00:00
postgres: wal receiver process
postgres 2288 2242 0 09:09 pts/0 00:00:00 ps -ef
postgres 2289 2242 0 09:09 pts/0 00:00:00 grep postgres
网上学习资料一大堆，但如果学到的知识不成体系，遇到问题时只是浅尝辄止，不再深入研究，那么很难做到真正的技术提升。
需要这份系统化的资料的朋友，可以添加v获取：vip1024b （备注软件测试）
一个人可以走的很快，但一群人才能走的更远！不论你是正从事it行业的老鸟或是对it行业感兴趣的新人，都欢迎加入我们的的圈子（技术交流、学习资源、职场吐槽、大厂内推、面试辅导），让我们一起学习成长！
s 2171 2169 0 09:04 ? 00:00:00 postgres: startup process waiting for 000000020000000000000012
postgres 2172 2169 0 09:04 ? 00:00:00 postgres: checkpointer process
postgres 2173 2169 0 09:04 ? 00:00:00 postgres: writer process
postgres 2175 2169 0 09:04 ? 00:00:00 postgres: stats collector process
root 2241 1992 0 09:06 pts/0 00:00:00 su - postgres
postgres 2242 2241 0 09:06 pts/0 00:00:00 -bash
postgres 2283 2169 0 09:07 ? 00:00:00
postgres: wal receiver process
postgres 2288 2242 0 09:09 pts/0 00:00:00 ps -ef
postgres 2289 2242 0 09:09 pts/0 00:00:00 grep postgres
网上学习资料一大堆，但如果学到的知识不成体系，遇到问题时只是浅尝辄止，不再深入研究，那么很难做到真正的技术提升。
需要这份系统化的资料的朋友，可以添加v获取：vip1024b （备注软件测试）
[外链图片转存中…(img-mlzaog5i-1713343409497)]
一个人可以走的很快，但一群人才能走的更远！不论你是正从事it行业的老鸟或是对it行业感兴趣的新人，都欢迎加入我们的的圈子（技术交流、学习资源、职场吐槽、大厂内推、面试辅导），让我们一起学习成长！
发表评论