Great question! You’re right that QuestDB has handy meta-functions for inspecting tables and columns, and it also lets you query runtime configuration properties directly via SQL. Here’s how to do it:

Querying Runtime Config with System Tables #

QuestDB includes a built-in system.configuration table that holds all active configuration values for your running instance—this covers both default settings and any custom overrides you’ve set (via config files, command-line args, or even runtime changes where supported).

To pull up every configuration property along with its value and where it came from, run this query:

SELECT name, value, source FROM system.configuration;

• name: The config key (like http.port or pg.max_connections)
• value: The currently active value of the setting
• source: Tells you if the value is a default, loaded from a config file, set via command line, etc.

Filter for Specific Settings #

If you only care about a particular property, narrow things down with a WHERE clause:

SELECT value FROM system.configuration WHERE name = 'query.max.concurrent';

Quick Notes #

• Some configs are read-only once QuestDB is running (they can only be set on startup), but you can still view their current values here.
• No extra setup is needed to access this table—it’s always available as long as you can connect to your QuestDB instance via SQL.

内容的提问来源于stack exchange，提问作者marregui