Re: explain plans with information about (modified) gucs - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: explain plans with information about (modified) gucs
Date
Msg-id 1edcee55-ea96-d123-199d-4c5f1fc5003b@2ndquadrant.com
Whole thread Raw
In response to Re: explain plans with information about (modified) gucs  (legrand legrand <legrand_legrand@hotmail.com>)
Responses Re: explain plans with information about (modified) gucs
List pgsql-hackers
Hi,

On 12/17/18 10:56 PM, legrand legrand wrote:
> what would you think about adding
>     search_path
> to that list ?
> 

Yeah, I've been thinking about that too. Currently it gets filtered out
because it's in the CLIENT_CONN_STATEMENT group, but the code only
includes QUERY_TUNING_*.

But we don't want to include everything from CLIENT_CONN_STATEMENT,
because that would include various kinds of timeouts, vacuuming
parameters, etc.

And the same issue applies to work_mem, which is in RESOURCES_MEM. And
of course, there's a lot of unrelated stuff in RESOURCES_MEM.

So I guess we'll need to enable QUERY_TUNING_* and then selectively a
couple of individual options from other groups.

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: legrand legrand
Date:
Subject: Re: explain plans with information about (modified) gucs
Next
From: Tom Lane
Date:
Subject: Re: explain plans with information about (modified) gucs