On 07/16/2019 10:56 PM, Andres Freund wrote:
Even after calling pg_logical_slot_get_changes() multiple times? What
does
SELECT * FROM pg_replication_slots; before and after multiple calls return?
Does manually forcing a checkpoint with CHECKPOINT; first on the primary
and then the standby "fix" the issue?
Yes,eventually it gets clean up -after firing multiple times get_changes
function or checkpoint or even both.
This same behavior we are able to see on MASTER -with or without patch.
but is this an old (existing) issue ?
b)pg_wal files are not recycling and every time it is creating new files
after firing get_changes function
I'm not sure what you mean by this. Are you saying that
pg_logical_slot_get_changes() causes WAL to be written?
No, when i said - created new WAL files , i meant -after each pg_bench
run NOT after executing get_changes.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
