| From: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_plan_advice |
| Date: | 2026-03-19 20:12:32 |
| Message-ID: | 1095d3fe-a6eb-4d83-866e-649d6f369908@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19/03/26 14:17, Robert Haas wrote:
> Before I forget, another idea that might help is to see if we can
> tweak meson.build to start running this particular test earlier. I
> thought about that during development, but I didn't actually do it. If
> the issue is that test being last to finish, that could help. If the
> issue is total resource consumption, it won't help with that.
>
We can add a 'priority' for the test:
'tap': {
'tests': [
't/001_replan_regress.pl',
],
+ 'test_kwargs': {'priority': 50},
},
Even if it's not help with resource consumption I think that it still
worth adding. It reduces from ~5m to ~4m on my machine.
--
Matheus Alcantara
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2026-03-19 20:14:41 | Re: pg_get__*_ddl consolidation |
| Previous Message | Heikki Linnakangas | 2026-03-19 20:11:14 | Re: Bug in MultiXact replay compat logic for older minor version after crash-recovery |