Re: pgsql: Wait for WAL summarization to catch up before creating .partial

2024-07-28 Thread Alexander Korotkov
On Sun, Jul 28, 2024 at 7:12 AM Tom Lane wrote: > Alexander Korotkov writes: > > It appears that I was late with my review [1]. But the new tap test > > could still use pgperltidy. > > I believe our current policy is that we're asking committers to > maintain pgindent cleanliness, but not pgperl

Re: pgsql: Wait for WAL summarization to catch up before creating .partial

2024-07-27 Thread Tom Lane
Alexander Korotkov writes: > It appears that I was late with my review [1]. But the new tap test > could still use pgperltidy. I believe our current policy is that we're asking committers to maintain pgindent cleanliness, but not pgperltidy (which is why BF member koel isn't checking pgperltidy)

Re: pgsql: Wait for WAL summarization to catch up before creating .partial

2024-07-27 Thread Alexander Korotkov
On Fri, Jul 26, 2024 at 10:01 PM Robert Haas wrote: > Wait for WAL summarization to catch up before creating .partial file. > > When a standby is promoted, CleanupAfterArchiveRecovery() may decide > to rename the final WAL file from the old timeline by adding ".partial" > to the name. If WAL summa