postgres-github.git / summary / log / commit / refs

commit    c210647aeb17692c138014235c7e7a2d9af73b87
Author:   Amit Kapila <akapila@postgresql.org>
Date:     Tue Apr 28 09:21:38 2026 +0000

    Fix xid_advance_interval when max_retention_duration is 0.
    
    When a subscription has retain_dead_tuples enabled and maxretention is
    zero (unlimited), adjust_xid_advance_interval() mistakenly caps
    xid_advance_interval to zero.
    
    This zero interval forces get_candidate_xid() to evaluate
    TimestampDifferenceExceeds() as always true, causing the apply worker to
    call GetOldestActiveTransactionId() for every WAL message. This
    leads to unnecessary ProcArrayLock acquisitions.
    
    Fix this by only capping the interval when maxretention > 0, allowing
    the exponential back-off to function properly.
    
    Author: SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
    Reviewed-by: shveta malik <shveta.malik@gmail.com>
    Reviewed-by: Nisha Moond <nisha.moond412@gmail.com>
    Discussion: https://postgr.es/m/CAHg+QDdKVnCLHot=AcoPpEiSyDzGz7wGYjAFHVOw57oDtmUDWQ@mail.gmail.com

[parent: 7424aac088e1]