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