| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jim Finnerty <jfinnert(at)amazon(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: explain plans with information about (modified) gucs |
| Date: | 2018-12-14 15:18:37 |
| Message-ID: | 9fd6dc95-738b-4b06-9616-844a4fc141b8@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/14/18 3:01 PM, Tomas Vondra wrote:
> On 12/14/18 2:05 PM, Jim Finnerty wrote:
>> You might want to only include the GUCs that are query tuning parameters,
>> i.e., those returned by:
>>
>> SELECT name, setting, category
>> FROM pg_settings
>> WHERE category LIKE 'Query Tuning%'
>> ORDER BY category, name;
>>
>
> Good idea! Thanks.
V2 filtering the options to QUERY_TUNING group (and subgroups).
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| explain-with-gucs-v2.diff | text/x-patch | 6.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-12-14 15:21:44 | Re: explain plans with information about (modified) gucs |
| Previous Message | Tom Lane | 2018-12-14 14:57:57 | Re: Upgrading pg_statistic to handle collation honestly |