Subject: Re: explain plans with information about (modified) gucs
To: legrand legrand <legrand_legrand@hotmail.com>,
 pgsql-hackers@postgresql.org
References: <e1791b4c-df9c-be02-edc5-7c8874944be0@2ndquadrant.com>
 <10561.1544800904@sss.pgh.pa.us>
 <c1282df1-43a8-0854-dfee-790d7dd9c93a@2ndquadrant.com>
 <631ae5c8-5581-6c5e-382c-2dcdb2e5c956@2ndquadrant.com>
 <1545083780942-0.post@n3.nabble.com>
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Message-ID: <1edcee55-ea96-d123-199d-4c5f1fc5003b@2ndquadrant.com>
Date: Mon, 17 Dec 2018 23:10:26 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.3.1
MIME-Version: 1.0
In-Reply-To: <1545083780942-0.post@n3.nabble.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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