From aa19b24def0667bd05c82046a32261902a92cdb1 Mon Sep 17 00:00:00 2001 From: Lana Brindley Date: Fri, 10 Sep 2021 22:59:24 +1000 Subject: [PATCH] Remove 'repeatable' isolation level from multinode docs (#361) Co-authored-by: Jacob Prall --- .../how-to-guides/multi-node-setup/required-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/timescaledb/how-to-guides/multi-node-setup/required-configuration.md b/timescaledb/how-to-guides/multi-node-setup/required-configuration.md index 3d19fcea1839..09743b6fc8d2 100644 --- a/timescaledb/how-to-guides/multi-node-setup/required-configuration.md +++ b/timescaledb/how-to-guides/multi-node-setup/required-configuration.md @@ -18,7 +18,7 @@ data nodes (if not already set, `150` is recommended). environment. * For consistency, if the transaction isolation level is set to `READ COMMITTED` it is automatically upgraded to `REPEATABLE READ` whenever a distributed operation - takes place. If the isolation level is `READ COMMITTED` or `SERIALIZABLE`, it is not changed. + takes place. If the isolation level is `SERIALIZABLE`, it is not changed. Each of the above settings parameters can be configured for the instance in `postgresql.conf`, typically located in the data