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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Robert Haas <rhaas(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Wait for WAL summarization to catch up before creating .partial
Date: 2024-07-28 04:12:39
Message-ID: 2167361.1722139959@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Alexander Korotkov <aekorotkov(at)gmail(dot)com> 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). We might get to that
eventually, but we're not there yet.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2024-07-28 08:10:35 pgsql: doc PG 17 relnotes: add "()" to PQsocketPoll mention
Previous Message Alexander Korotkov 2024-07-28 03:40:32 Re: pgsql: Wait for WAL summarization to catch up before creating .partial