Re: pgsql: Add TAP test for archive_cleanup_command and recovery_end_comman

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Add TAP test for archive_cleanup_command and recovery_end_comman
Date: 2022-04-08 16:36:08
Message-ID: 3683274.1649435768@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2022-04-07 13:57:45 -0400, Tom Lane wrote:
>> Yeah, with only one instance it could just be cosmic rays or something.

Not cosmic rays: skink has shown the same symptom three times running.
Looks like maybe the archive_cleanup_command itself is doing something
it shouldn't?

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2022-04-08 18:23:19 pgsql: Fix busted .gitignore entry.
Previous Message Robert Haas 2022-04-08 15:50:59 Re: API stability [was: pgsql: Fix possible recovery trouble if TRUNCATE overlaps a checkpoint.]

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2022-04-08 16:44:12 Re: Lowering the ever-growing heap->pd_lower
Previous Message Zhihong Yu 2022-04-08 16:28:43 Re: Defer selection of asynchronous subplans until the executor initialization stage