| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Justin Clift <justin(at)postgresql(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, nikhil raj <nikhilraj474(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, NIKITA PATEL <patelnikita1411(at)gmail(dot)com>, Patel Khushbu <patelkhushbu2067(at)gmail(dot)com> |
| Subject: | Re: Significant Execution Time Difference Between PG13.14 and PG16.4 for Query on information_schema Tables. |
| Date: | 2024-08-27 10:14:07 |
| Message-ID: | CAApHDvr6igx9SPQs3n_K5WwvTdYwhZ1LzP6qOfiGFNbUHXOCyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Tue, 27 Aug 2024 at 18:00, Justin Clift <justin(at)postgresql(dot)org> wrote:
> As a general thought, seeing that this might be an actual problem
> should some kind of automated testing be added that checks for
> performance regressions like this?
We normally try to catch these sorts of things with regression tests.
Of course, that requires having a test that would catch a particular
problem, which we don't seem to have for this particular case. A
performance test would also require testing a particular scenario, so
I don't see why that's better. A regression test is better suited as
there's no middle ground between pass and fail.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dominique Devienne | 2024-08-27 10:23:52 | Re: Using PQsocketPoll() for PIPELINE mode |
| Previous Message | Shyam Duraiswami | 2024-08-27 09:36:30 | Analytics on PostgresQL Advisory |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2024-08-27 10:14:46 | Re: Parallel CREATE INDEX for GIN indexes |
| Previous Message | Thomas Munro | 2024-08-27 10:03:31 | Re: Segfault in jit tuple deforming on arm64 due to LLVM issue |