From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Sergei Agalakov <sergei.agalakov@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: explain plans with information about (modified) gucs
Date: Mon, 14 Jan 2019 19:13:07 -0300
Message-ID: <201901142213.gt7vdg65pp4d@alvherre.pgsql> (raw)
In-Reply-To: <5396e093-ed6b-5962-2ed5-337a0425160b@2ndquadrant.com>
On 2019-Jan-14, Tomas Vondra wrote:
> The one slightly annoying issue is that currently all the options are
> formatted as text, including e.g. cpu_tuple_cost. That's because the GUC
> options may have show hook, so I can't access the value directly (not
> sure if there's an option around it).
I think the problem is that you'd have to know how to print the value,
which can be in one of several different C types. You'd have to grow
some more infrastructure in the GUC tables, I think, and that doesn't
seem worth the trouble. Printing as text seems enough.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, tomas.vondra@2ndquadrant.com, sergei.agalakov@gmail.com
Subject: Re: explain plans with information about (modified) gucs
In-Reply-To: <201901142213.gt7vdg65pp4d@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox