From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, vignesh C <vignesh21(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Test to dump and restore objects left behind by regression |
Date: | 2025-04-02 09:19:26 |
Message-ID: | 202504020919.lkpuxdtu75hp@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2025-Apr-02, Ashutosh Bapat wrote:
> I have closed the CF entry
> https://commitfest.postgresql.org/patch/4564/ committed. I will
> create another CF entry to park --no-statistics reversal change. That
> way, we will know when statistics dump/restore has become stable.
No commitfest entry please. Better to add an open item on the wiki
page.
https://wiki.postgresql.org/wiki/Open_Items
> Yes. Few animals that I sampled, the test is finishing pretty early
> even though it's taking longer than many other tests. But it's not the
> longest. I also looked at red animals, but none of them report this
> test to be failing.
Yay. Still, I don't think this is a reason not to seek a way to
optimize the test run time in one of the ways we discussed.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Every machine is a smoke machine if you operate it wrong enough."
https://twitter.com/libseybieda/status/1541673325781196801
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2025-04-02 09:34:07 | Re: Fix 035_standby_logical_decoding.pl race conditions |
Previous Message | Alvaro Herrera | 2025-04-02 09:17:38 | Re: Support NOT VALID / VALIDATE constraint options for named NOT NULL constraints |