postgresql PG_WAL非常大

8hhllhi2  于 2023-01-08  发布在  PostgreSQL
关注(0)|答案(1)|浏览(438)

我有一个包含3个节点的Postgres群集:ETCD+赞助商+Postgres 13.
现在有一个不断增长的pg_wal文件夹的问题。它现在包含5127个文件。在互联网上搜索后,我发现了一篇文章,建议您注意以下数据库参数(它们在案件发生时的含义是这样的):

archive_mode off;
wal_level replica;
max_wal_size 1G;

SELECT * FROM pg_replication_slots;

postgres=# SELECT * FROM pg_replication_slots;
-[ RECORD 1 ]-------+------------
slot_name           | db2
plugin              |
slot_type           | physical
datoid              |
database            |
temporary           | f
active              | t
active_pid          | 2247228
xmin                |
catalog_xmin        |
restart_lsn         | 2D/D0ADC308
confirmed_flush_lsn |
wal_status          | reserved
safe_wal_size       |
-[ RECORD 2 ]-------+------------
slot_name           | db1
plugin              |
slot_type           | physical
datoid              |
database            |
temporary           | f
active              | t
active_pid          | 2247227
xmin                |
catalog_xmin        |
restart_lsn         | 2D/D0ADC308
confirmed_flush_lsn |
wal_status          | reserved
safe_wal_size       |

Patroni集群的所有其他功能都正常工作(切换、重新初始化、复制);

root@srvdb3:~# patronictl -c /etc/patroni/patroni.yml list
+ Cluster: mobile (7173650272103321745) --+----+-----------+
| Member | Host       | Role    | State   | TL | Lag in MB |
+--------+------------+---------+---------+----+-----------+
| db1    | 10.01.1.01 | Replica | running | 17 |         0 |
| db2    | 10.01.1.02 | Replica | running | 17 |         0 |
| db3    | 10.01.1.03 | Leader  | running | 17 |           |
+--------+------------+---------+---------+----+-----------+

守护神-编辑:

loop_wait: 10
maximum_lag_on_failover: 1048576
postgresql:
  parameters:
    checkpoint_timeout: 30
    hot_standby: 'on'
    max_connections: '1100'
    max_replication_slots: 5
    max_wal_senders: 5
    shared_buffers: 2048MB
    wal_keep_segments: 5120
    wal_level: replica
  use_pg_rewind: true
  use_slots: true
retry_timeout: 10
ttl: 100

帮帮忙,怎么回事?
这是我在pg_stat_archiver中看到的内容:

postgres=# select * from pg_stat_archiver;
-[ RECORD 1 ]------+------------------------------
archived_count     | 0
last_archived_wal  |
last_archived_time |
failed_count       | 0
last_failed_wal    |
last_failed_time   |
stats_reset        | 2023-01-06 10:21:45.615312+00
vlju58qv

vlju58qv1#

如果wal_keep_segments设置为5120,那么pg_wal中有5127个WAL段是完全正常的,因为PostgreSQL将始终保留至少5120个旧的WAL段。如果这对您来说太多,请减小该参数。如果您正在使用复制插槽,唯一的缺点是您可能只能在故障转移后立即使用pg_rewind

相关问题