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

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 10:43:18
Message-ID: CAPpHfdsQnV-bWaNcKzUCjqZxvfdRG-3m-JtbOox9U+ygX=ee-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sun, Jul 28, 2024 at 7:12 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.

Got it, thank you. Sorry for noise, then.

------
Regards,
Alexander Korotkov
Supabase

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Alexander Korotkov 2024-07-28 11:04:14 pgsql: amcheck: Optimize speed of checking for unique constraint violat
Previous Message David Rowley 2024-07-28 10:24:31 pgsql: Fix incorrect return value for pg_size_pretty(bigint)