Re: Another modest proposal for reducing CLOBBER_CACHE_ALWAYS runtime

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: Another modest proposal for reducing CLOBBER_CACHE_ALWAYS runtime
Дата
Msg-id CAApHDvrGnVmZ+cZvoNLO-wDhJ+ACP9dSKOcXw=6F0D24=hYZ-g@mail.gmail.com
обсуждение исходный текст
Ответ на Another modest proposal for reducing CLOBBER_CACHE_ALWAYS runtime  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Another modest proposal for reducing CLOBBER_CACHE_ALWAYS runtime
Список 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: vignesh C
Дата:
Сообщение: Re: [HACKERS] logical decoding of two-phase transactions
Следующее
От: Amit Langote
Дата:
Сообщение: Re: Allow batched insert during cross-partition updates