Re: numeric_big in make check?

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: numeric_big in make check?
Date: 2024-02-20 13:46:16
Message-ID: 3014F290-5BE8-4397-9276-830D5DB0A297@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 20 Feb 2024, at 14:23, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:

> If we did that, numeric_big would be even further down the list of
> expensive tests, and I'd say it should be run by default.

My motivation for raising this was to get a test which is executed as part of
parallel_schedule to make failures aren't missed. If we get there by slimming
down numeric_big to keep the unique coverage then that sounds like a good plan
to me.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2024-02-20 13:55:21 Re: A new message seems missing a punctuation
Previous Message vignesh C 2024-02-20 13:34:57 Re: speed up a logical replica setup