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

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

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

2024-07-26 Thread Robert Haas
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 summarization is enabled and this file is renamed before its

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

2024-07-26 Thread Robert Haas
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 summarization is enabled and this file is renamed before its