Re: A recent message added to pg_upgade

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, smithpb2250(at)gmail(dot)com, bharath(dot)rupireddyforpostgres(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: A recent message added to pg_upgade
Date: 2025-07-11 03:48:20
Message-ID: 1670621.1752205700@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:
> Thanks for the patch and verification. It looks good to me as well.
> Shall we commit this today or wait for beta2 as per email by Tom [1]?
> We are on the borderline to see that most of the BF members have run
> with this, but as the change is straightforward, I think we can
> proceed.

Release freeze doesn't start till Saturday, so if you feel
comfortable with this change, go ahead. Waiting till closer
to the deadline does not improve your odds...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhang Mingli 2025-07-11 04:03:46 Re: Adding some error context for lock wait failures
Previous Message shveta malik 2025-07-11 03:45:54 Re: [WIP]Vertical Clustered Index (columnar store extension) - take2