This option controls what functions are available in the PostgreSQL query builder.
</info-popover>
</span>
<spanclass="gf-form-select-wrapper">
<selectclass="gf-form-input gf-size-auto"ng-model="ctrl.current.jsonData.postgresVersion"ng-options="f.value as f.name for f in ctrl.postgresVersions"></select>
This option controls what functions are available in the PostgreSQL query builder.
</info-popover>
</span>
<spanclass="gf-form-select-wrapper">
<selectclass="gf-form-input gf-size-auto"ng-model="ctrl.current.jsonData.postgresVersion"ng-options="f.value as f.name for f in ctrl.postgresVersions"></select>
<ahref="https://github.com/timescale/timescaledb"class="pointer"target="_blank">TimescaleDB</a> is a time-series database built as a PostgreSQL extension. If enabled, Grafana will use <code>time_bucket</code> in the <code>$__timeGroup</code> macro and display TimescaleDB specific aggregate functions in the query builder.
<ahref="https://github.com/timescale/timescaledb"class="pointer"target="_blank">TimescaleDB</a> is a time-series database built as a PostgreSQL extension. If enabled, Grafana will use <code>time_bucket</code> in the <code>$__timeGroup</code> macro and display TimescaleDB specific aggregate functions in the query builder.
</p>
</div>
</div>
...
...
@@ -145,13 +145,13 @@
<divclass="gf-form-group">
<divclass="grafana-info-box">
<h5>User Permission</h5>
<p>
The database user should only be granted SELECT permissions on the specified database & tables you want to query.
Grafana does not validate that queries are safe so queries can contain any SQL statement. For example, statements
like <code>DELETE FROM user;</code> and <code>DROP TABLE user;</code> would be executed. To protect against this we
<strong>Highly</strong> recommmend you create a specific PostgreSQL user with restricted permissions.
</p>
</div>
<divclass="grafana-info-box">
<h5>User Permission</h5>
<p>
The database user should only be granted SELECT permissions on the specified database & tables you want to query.
Grafana does not validate that queries are safe so queries can contain any SQL statement. For example, statements
like <code>DELETE FROM user;</code> and <code>DROP TABLE user;</code> would be executed. To protect against this we
<strong>Highly</strong> recommmend you create a specific PostgreSQL user with restricted permissions.