|From:||Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>|
|Cc:||thomas(dot)munro(at)enterprisedb(dot)com, sk(at)zsrv(dot)org, michael(dot)paquier(at)gmail(dot)com, andres(at)anarazel(dot)de, peter(dot)eisentraut(at)2ndquadrant(dot)com|
|Subject:||Re: [HACKERS] Restricting maximum keep segments by repslots|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Hello. This is the reabased version of slot-limit feature.
This patch limits maximum WAL segments to be kept by replication
slots. Replication slot is useful to avoid desync with replicas
after temporary disconnection but it is dangerous when some of
replicas are lost. The WAL space can be exhausted and server can
PANIC in the worst case. This can prevent the worst case having a
benefit from replication slots using a new GUC variable
This is a feature mentioned in the documentation.
> In lieu of using replication slots, it is possible to prevent the
> removal of old WAL segments using wal_keep_segments, or by
> storing the segments in an archive using
> archive_command. However, these methods often result in retaining
> more WAL segments than required, whereas replication slots retain
> only the number of segments known to be needed. An advantage of
> these methods is that they bound the space requirement for
> pg_wal; there is currently no way to do this using replication
The previous patche files doesn't have version number so I let
the attached latest version be v2.
The body of the limiting feature
Shows the status of WAL rataining in pg_replication_slot view
TAP test for this feature
Documentation, as the name.
NTT Open Source Software Center
|Next Message||Amit Langote||2018-06-26 07:37:28||Re: partition tree inspection functions|
|Previous Message||Jeevan Ladhe||2018-06-26 07:22:44||Re: "Access privileges" is missing after pg_dumpall|