Re: Test to dump and restore objects left behind by regression - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Test to dump and restore objects left behind by regression
Date
Msg-id 202508051433.ebznuqrxt4b2@alvherre.pgsql
Whole thread Raw
In response to Re: Test to dump and restore objects left behind by regression  (Andres Freund <andres@anarazel.de>)
Responses Re: Test to dump and restore objects left behind by regression
List pgsql-hackers
Hello,

On 2025-Apr-04, Andres Freund wrote:
 
> FWIW, with cassert and -O2, it's:
> 
> 17:
>     real    0m53.981s
>     user    3m22.837s
>     sys    3m24.237s
> 
> HEAD:
>     real    1m19.749s
>     user    4m54.526s
>     sys    4m15.657s
> 
> so this isn't just due to me using -O0. A 48% increase is better than a 60%
> increase, but it's still not sustainable.

I happened to notice that this item was still open in the commitfest,
and rereading the thread I now have second thoughts about having it
enabled by default, giving your complaints about speed.  How about
applying this to 18 and master?

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"This is a foot just waiting to be shot"                (Andrew Dunstan)

Attachment

pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: Implement waiting for wal lsn replay: reloaded
Next
From: Dmitry
Date:
Subject: Re: IPC/MultixactCreation on the Standby server