From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Robert Haas <rhaas@postgresql.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Wait for WAL summarization to catch up before creating .partial
Date: Sun, 28 Jul 2024 00:12:39 -0400
Message-ID: <2167361.1722139959@sss.pgh.pa.us> (raw)
In-Reply-To: <CAPpHfdsZN0X52_HxHsLRD2Kp8=xkz28Nr-cSgxosaaXKORD3oA@mail.gmail.com>
References: <E1sXQCH-001Lc6-Hd@gemulon.postgresql.org>
<CAPpHfdsZN0X52_HxHsLRD2Kp8=xkz28Nr-cSgxosaaXKORD3oA@mail.gmail.com>
Alexander Korotkov <aekorotkov@gmail.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, aekorotkov@gmail.com, rhaas@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Wait for WAL summarization to catch up before creating .partial
In-Reply-To: <2167361.1722139959@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox