Re: Another modest proposal for reducing CLOBBER_CACHE_ALWAYS runtime

David Rowley <dgrowleyml@gmail.com>

From: David Rowley <dgrowleyml@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2021-05-10T06:57:48Z
Lists: pgsql-hackers
On Mon, 10 May 2021 at 18:04, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> I dug into it and found that the core issue is much like that in
> opr_sanity.sql, namely that we're repeating this plpgsql function
> $bignum times:
>
> CREATE FUNCTION leak(integer,integer) RETURNS boolean
>   AS $$begin return $1 < $2; end$$
>   LANGUAGE plpgsql immutable;

> real    293m31.054s
> to
> real    1m47.807s
>
> Yes, really.

That's quite impressive.

I've very much in favour of this change. Making it more realistic to
run the regression tests on a CLOBBER_CACHE_ALWAYS builds before a
commit is a very worthy goal and this is a big step towards that.
Nice.

David



Commits

  1. Reduce runtime of privileges.sql test under CLOBBER_CACHE_ALWAYS.