Re: pg_plan_advice - Mailing list pgsql-hackers

From Matheus Alcantara
Subject Re: pg_plan_advice
Date
Msg-id 1095d3fe-a6eb-4d83-866e-649d6f369908@gmail.com
Whole thread Raw
In response to Re: pg_plan_advice  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: pg_plan_advice
List 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 by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Bug in MultiXact replay compat logic for older minor version after crash-recovery
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_get__*_ddl consolidation