From 7050d7d1b41b39be6ca037180d8458606385a1b6 Mon Sep 17 00:00:00 2001 From: loquacity Date: Fri, 17 Dec 2021 16:19:41 +1000 Subject: [PATCH 1/7] change txt to yaml for prism.js highlighting --- timescaledb/how-to-guides/configuration/telemetry.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/timescaledb/how-to-guides/configuration/telemetry.md b/timescaledb/how-to-guides/configuration/telemetry.md index 14bbd594b0..4c36bc9891 100644 --- a/timescaledb/how-to-guides/configuration/telemetry.md +++ b/timescaledb/how-to-guides/configuration/telemetry.md @@ -83,14 +83,14 @@ If you disable telemetry, the version checking functionality is also disabled. ### Disabling telemetry -1. Open your PostgreSQL configuration file, and locate - the `timescaledb.telemetry_level` parameter. See our +1. Open your PostgreSQL configuration file, and locate the + `timescaledb.telemetry_level` parameter. See our [PostgreSQL configuration file][postgres-config] instructions for locating and opening the file. 1. Change the parameter setting to `off`: - ```txt - timescaledb.telemetry_level=off - ``` + ```yaml + timescaledb.telemetry_level=off + ``` 1. Reload the configuration file: ```bash pg_ctl @@ -112,7 +112,7 @@ If you disable telemetry, the version checking functionality is also disabled. [PostgreSQL configuration file][postgres-config] instructions for locating and opening the file. 1. Change the parameter setting to `off`: - ```txt + ```yaml timescaledb.telemetry_level=basic ``` 1. Reload the configuration file: From 8db25f9b6cd904d07d6150c85d786255b503228e Mon Sep 17 00:00:00 2001 From: loquacity Date: Fri, 17 Dec 2021 16:37:33 +1000 Subject: [PATCH 2/7] java highlight --- timescaledb/how-to-guides/configuration/telemetry.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/timescaledb/how-to-guides/configuration/telemetry.md b/timescaledb/how-to-guides/configuration/telemetry.md index 4c36bc9891..2d2cd33008 100644 --- a/timescaledb/how-to-guides/configuration/telemetry.md +++ b/timescaledb/how-to-guides/configuration/telemetry.md @@ -8,8 +8,7 @@ appropriately seeded random number generators. This is an example of the JSON data file that is sent to our servers about a specific deployment: - -```javascript +```java { "db_uuid": "26917841-2fc0-48fd-b096-ba19b3fda98f", "license": { From c3fa6aab5edc4929b7627ead627f09d231e601be Mon Sep 17 00:00:00 2001 From: loquacity Date: Fri, 17 Dec 2021 16:37:56 +1000 Subject: [PATCH 3/7] except it's json --- timescaledb/how-to-guides/configuration/telemetry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/timescaledb/how-to-guides/configuration/telemetry.md b/timescaledb/how-to-guides/configuration/telemetry.md index 2d2cd33008..3f9798a668 100644 --- a/timescaledb/how-to-guides/configuration/telemetry.md +++ b/timescaledb/how-to-guides/configuration/telemetry.md @@ -8,7 +8,7 @@ appropriately seeded random number generators. This is an example of the JSON data file that is sent to our servers about a specific deployment: -```java +```json { "db_uuid": "26917841-2fc0-48fd-b096-ba19b3fda98f", "license": { From f0308e136803e7006f3363f51eba6818301e2264 Mon Sep 17 00:00:00 2001 From: loquacity Date: Fri, 17 Dec 2021 16:39:18 +1000 Subject: [PATCH 4/7] reflow first step --- timescaledb/how-to-guides/configuration/telemetry.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/timescaledb/how-to-guides/configuration/telemetry.md b/timescaledb/how-to-guides/configuration/telemetry.md index 3f9798a668..e6bbe54687 100644 --- a/timescaledb/how-to-guides/configuration/telemetry.md +++ b/timescaledb/how-to-guides/configuration/telemetry.md @@ -82,8 +82,9 @@ If you disable telemetry, the version checking functionality is also disabled. ### Disabling telemetry -1. Open your PostgreSQL configuration file, and locate the - `timescaledb.telemetry_level` parameter. See our + +1. Open your PostgreSQL configuration file, and locate + the `timescaledb.telemetry_level` parameter. See our [PostgreSQL configuration file][postgres-config] instructions for locating and opening the file. 1. Change the parameter setting to `off`: @@ -106,6 +107,7 @@ If you disable telemetry, the version checking functionality is also disabled. ### Enabling telemetry + 1. Open your PostgreSQL configuration file, and locate the `timescaledb.telemetry_level` parameter. See our [PostgreSQL configuration file][postgres-config] instructions for locating From 402ba4c36a15440e7b78d9082b31787f290ad502 Mon Sep 17 00:00:00 2001 From: loquacity Date: Fri, 17 Dec 2021 16:50:39 +1000 Subject: [PATCH 5/7] spaces? --- timescaledb/how-to-guides/configuration/telemetry.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/timescaledb/how-to-guides/configuration/telemetry.md b/timescaledb/how-to-guides/configuration/telemetry.md index e6bbe54687..761b31ff8f 100644 --- a/timescaledb/how-to-guides/configuration/telemetry.md +++ b/timescaledb/how-to-guides/configuration/telemetry.md @@ -89,7 +89,7 @@ If you disable telemetry, the version checking functionality is also disabled. and opening the file. 1. Change the parameter setting to `off`: ```yaml - timescaledb.telemetry_level=off + timescaledb.telemetry_level=off ``` 1. Reload the configuration file: ```bash @@ -114,7 +114,7 @@ If you disable telemetry, the version checking functionality is also disabled. and opening the file. 1. Change the parameter setting to `off`: ```yaml - timescaledb.telemetry_level=basic + timescaledb.telemetry_level=basic ``` 1. Reload the configuration file: ```bash From 4665a528dfee41e22fb046b5e24e538711a3d7cb Mon Sep 17 00:00:00 2001 From: loquacity Date: Fri, 17 Dec 2021 16:53:00 +1000 Subject: [PATCH 6/7] spaces? --- .../how-to-guides/configuration/telemetry.md | 34 +++++++++---------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/timescaledb/how-to-guides/configuration/telemetry.md b/timescaledb/how-to-guides/configuration/telemetry.md index 761b31ff8f..5323c5c433 100644 --- a/timescaledb/how-to-guides/configuration/telemetry.md +++ b/timescaledb/how-to-guides/configuration/telemetry.md @@ -83,24 +83,24 @@ If you disable telemetry, the version checking functionality is also disabled. ### Disabling telemetry -1. Open your PostgreSQL configuration file, and locate - the `timescaledb.telemetry_level` parameter. See our - [PostgreSQL configuration file][postgres-config] instructions for locating - and opening the file. -1. Change the parameter setting to `off`: - ```yaml +1. Open your PostgreSQL configuration file, and locate + the `timescaledb.telemetry_level` parameter. See our + [PostgreSQL configuration file][postgres-config] instructions for locating + and opening the file. +1. Change the parameter setting to `off`: + ```yaml timescaledb.telemetry_level=off - ``` -1. Reload the configuration file: - ```bash - pg_ctl - ``` -1. Alternatively, you can use this command at the `psql` prompt, as the root - user: - ```sql - ALTER [SYSTEM | DATABASE | USER] { *db_name* | *role_specification* } SET timescaledb.telemetry_level=off - ``` - This command disables telemetry for the specified system, database, or user. + ``` +1. Reload the configuration file: + ```bash + pg_ctl + ``` +1. Alternatively, you can use this command at the `psql` prompt, as the root + user: + ```sql + ALTER [SYSTEM | DATABASE | USER] { *db_name* | *role_specification* } SET timescaledb.telemetry_level=off + ``` + This command disables telemetry for the specified system, database, or user. From f13c76c796f417ea239d700e0e32cabcfb81c154 Mon Sep 17 00:00:00 2001 From: Jacob Prall Date: Fri, 17 Dec 2021 06:02:11 -0800 Subject: [PATCH 7/7] fix --- .../how-to-guides/configuration/telemetry.md | 34 +++++++++---------- .../multinode-maintenance.md | 2 +- 2 files changed, 17 insertions(+), 19 deletions(-) diff --git a/timescaledb/how-to-guides/configuration/telemetry.md b/timescaledb/how-to-guides/configuration/telemetry.md index 5323c5c433..be12877802 100644 --- a/timescaledb/how-to-guides/configuration/telemetry.md +++ b/timescaledb/how-to-guides/configuration/telemetry.md @@ -108,24 +108,22 @@ If you disable telemetry, the version checking functionality is also disabled. ### Enabling telemetry -1. Open your PostgreSQL configuration file, and locate - the `timescaledb.telemetry_level` parameter. See our - [PostgreSQL configuration file][postgres-config] instructions for locating - and opening the file. -1. Change the parameter setting to `off`: - ```yaml - timescaledb.telemetry_level=basic - ``` -1. Reload the configuration file: - ```bash - pg_ctl - ``` -1. Alternatively, you can use this command at the `psql` prompt, as the root - user: - ```sql - ALTER [SYSTEM | DATABASE | USER] { *db_name* | *role_specification* } SET timescaledb.telemetry_level=basic - ``` - This command enables telemetry for the specified system, database, or user. +1. Open your PostgreSQL configuration file, and locate the 'timescaledb.telemetry_level' + parameter. See our [PostgreSQL configuration file][postgres-config] instructions for locating and opening the file. + +1. Change the parameter setting to 'off': + ```yaml + timescaledb.telemetry_level=basic + ``` +1. Reload the configuration file: + ```bash + pg_ctl + ``` +1. Alternatively, you can use this command at the `psql` prompt, as the root user: + ```sql + ALTER [SYSTEM | DATABASE | USER] { *db_name* | *role_specification* } SET timescaledb.telemetry_level=basic + ``` + This command enables telemetry for the specified system, database, or user. diff --git a/timescaledb/how-to-guides/multinode-timescaledb/multinode-maintenance.md b/timescaledb/how-to-guides/multinode-timescaledb/multinode-maintenance.md index e9090c5cbf..e1c0b5938b 100644 --- a/timescaledb/how-to-guides/multinode-timescaledb/multinode-maintenance.md +++ b/timescaledb/how-to-guides/multinode-timescaledb/multinode-maintenance.md @@ -5,11 +5,11 @@ access node keeps a log of distributed transactions so that nodes that haven't completed their part of the distributed transaction can complete it later when they become available. This transaction log requires regular cleanup to remove transactions that have completed, and complete those that haven't. - We highly recommended that you configure the access node to run a maintenance job that regularly cleans up any unfinished distributed transactions. The custom maintenance job can be run as a user-defined action. For example: + ```sql CREATE OR REPLACE PROCEDURE data_node_maintenance(job_id int, config jsonb) LANGUAGE SQL AS