Re: pg_plan_advice
| От | Matheus Alcantara |
|---|---|
| Тема | Re: pg_plan_advice |
| Дата | |
| Msg-id | 1095d3fe-a6eb-4d83-866e-649d6f369908@gmail.com обсуждение исходный текст |
| Ответ на | Re: pg_plan_advice (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: pg_plan_advice
|
| Список | 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
В списке pgsql-hackers по дате отправления: