Re: explain plans with information about (modified) gucs

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: Sergei Agalakov <sergei(dot)agalakov(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: explain plans with information about (modified) gucs
Date: 2019-01-14 22:13:07
Message-ID: 201901142213.gt7vdg65pp4d@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

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
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Arseny Sher 2019-01-14 22:16:33 Re: [HACKERS] logical decoding of two-phase transactions
Previous Message Peter Geoghegan 2019-01-14 21:46:32 Re: Non-deterministic IndexTuple toast compression from index_form_tuple() + amcheck false positives