Re: WAL segments removed from primary despite the fact that logical replication slot needs it.

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-bugs mailing list <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
Date: 2022-11-17 10:26:57
Message-ID: Y3YMcdBQEBgGwq+Y@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Nov 16, 2022 at 11:25:12PM -0800, Andres Freund wrote:
> Perhaps a stupid question - are you using max_slot_wal_keep_size? And what's
> your wal_segment_size? And wal_keep_size?

Are we talking about pg12 side?

=> select name, setting from pg_settings where name ~ 'wal';
name │ setting
══════════════════════════════╪═══════════
max_wal_senders │ 50
max_wal_size │ 49152
min_wal_size │ 256
wal_block_size │ 8192
wal_buffers │ 2048
wal_compression │ on
wal_consistency_checking │
wal_init_zero │ on
wal_keep_segments │ 1000
wal_level │ logical
wal_log_hints │ off
wal_receiver_status_interval │ 10
wal_receiver_timeout │ 60000
wal_recycle │ on
wal_retrieve_retry_interval │ 5000
wal_segment_size │ 16777216
wal_sender_timeout │ 60000
wal_sync_method │ fdatasync
wal_writer_delay │ 200
wal_writer_flush_after │ 128
(20 rows)

max_slot_wal_keep_size was added in pg13, afaik. and wel_keep_* was
_segments in pg 12.

Best regards,

depesz

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2022-11-17 12:59:54 Re: Possible RegEx bug for lower-case a and s characters
Previous Message Andres Freund 2022-11-17 08:02:58 Re: WAL segments removed from primary despite the fact that logical replication slot needs it.