From 8bd5cdbe9faa8299aa925b0198998d335d9a8d65 Mon Sep 17 00:00:00 2001 From: Arve Knudsen Date: Fri, 22 Jan 2021 10:14:12 +0100 Subject: [PATCH] Postgres: Fix indentation (#30531) Signed-off-by: Arve Knudsen --- .../datasource/postgres/partials/config.html | 146 +++++++++--------- 1 file changed, 73 insertions(+), 73 deletions(-) diff --git a/public/app/plugins/datasource/postgres/partials/config.html b/public/app/plugins/datasource/postgres/partials/config.html index f9bd4d28b3c..3fe1ff60ea6 100644 --- a/public/app/plugins/datasource/postgres/partials/config.html +++ b/public/app/plugins/datasource/postgres/partials/config.html @@ -2,21 +2,21 @@

PostgreSQL Connection

-
- Host - -
+
+ Host + +
-
- Database - -
+
+ Database + +
-
-
- User - -
+
+
+ User + +
Connection limits
-
- Max open - - - The maximum number of open connections to the database. If Max idle connections is greater than 0 and the - Max open connections is less than Max idle connections, then Max idle connections will be - reduced to match the Max open connections limit. If set to 0, there is no limit on the number of open - connections. - -
-
- Max idle - - - The maximum number of connections in the idle connection pool. If Max open connections is greater than 0 but - less than the Max idle connections, then the Max idle connections will be reduced to match the - Max open connections limit. If set to 0, no idle connections are retained. - -
-
- Max lifetime - - - The maximum amount of time in seconds a connection may be reused. If set to 0, connections are reused forever. - -
+
+ Max open + + + The maximum number of open connections to the database. If Max idle connections is greater than 0 and the + Max open connections is less than Max idle connections, then Max idle connections will be + reduced to match the Max open connections limit. If set to 0, there is no limit on the number of open + connections. + +
+
+ Max idle + + + The maximum number of connections in the idle connection pool. If Max open connections is greater than 0 but + less than the Max idle connections, then the Max idle connections will be reduced to match the + Max open connections limit. If set to 0, no idle connections are retained. + +
+
+ Max lifetime + + + The maximum amount of time in seconds a connection may be reused. If set to 0, connections are reused forever. + +

PostgreSQL details

-
- - Version - - This option controls what functions are available in the PostgreSQL query builder. - - - - - -
-
- +
+ + Version + + This option controls what functions are available in the PostgreSQL query builder. + + + + + +
+
+ -
+
-
-
- Min time interval - +
+ Min time interval + - - A lower limit for the auto group by time interval. Recommended to be set to write frequency, - for example 1m if your data is written every minute. - -
-
+ + A lower limit for the auto group by time interval. Recommended to be set to write frequency, + for example 1m if your data is written every minute. + +
+

- TimescaleDB is a time-series database built as a PostgreSQL extension. If enabled, Grafana will use time_bucket in the $__timeGroup macro and display TimescaleDB specific aggregate functions in the query builder. + TimescaleDB is a time-series database built as a PostgreSQL extension. If enabled, Grafana will use time_bucket in the $__timeGroup macro and display TimescaleDB specific aggregate functions in the query builder.

@@ -145,13 +145,13 @@
-
-
User Permission
-

- 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 DELETE FROM user; and DROP TABLE user; would be executed. To protect against this we - Highly recommmend you create a specific PostgreSQL user with restricted permissions. -

-
+
+
User Permission
+

+ 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 DELETE FROM user; and DROP TABLE user; would be executed. To protect against this we + Highly recommmend you create a specific PostgreSQL user with restricted permissions. +

+