From 8c4853ab253b426c2158e9eee01ad11d20f19f69 Mon Sep 17 00:00:00 2001
From: rolandstirnimann <roland.stirnimann@accenture.com>
Date: Tue, 6 Sep 2022 16:27:25 +0200
Subject: [PATCH] Change log update for release 2.1

---
 CHANGELOG.md | 17 ++++++++++++-----
 1 file changed, 12 insertions(+), 5 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 893d96a..395b7e2 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,21 +1,28 @@
-### v2.0
+## v2.1
+* Improved cluster detection (issue #12) to reduce performance overhead
+* Improved `scriptmgr.sh prep` call (issue #11)
+  * Recreate file `$PGBASENV_BASE/scripts/.run.${TVD_PGVERSION}` only if content of `$PGBASENV_BASE/scripts/*.sql` changes
+  * File locking for `$PGBASENV_BASE/scripts/.run.${TVD_PGVERSION}` to avoid concurrency issues
+* Fixed issue #10 related to VERSION_NAME query in .psqlrc
+
+## v2.0
 * fixed an issues in detecting non-ssl Postgres Homes
 
-### v1.9
+## v1.9
 * `pgsetenv.sh` now accepts `--noscan` option. It will source the *pgBaseEnv* without scanning the filesystem. This argument can be used also in `$HOME/.pgbasenv_profile` to prevent filesystem scan every time on login.
   
 
-### v1.5
+## v1.5
 
 * Additional information about standby status and incoming data stream will be reported. Now status of the wal receiver and master node:port will be reported. Standby status string: `Cluster role: STANDBY [ Status: streaming Master: masternode:5435 In recovery: YES ]`. As usual all these information will be available from the evn variables `TVD_PGMASTER_HOST`, `TVD_PGMASTER_PORT` and `TVD_PGSTANDBY_STATUS`.
 * Timeouts was added to find commands to prevent hangs. Parameter `PGBASENV_SEARCH_TIMEOUT` can be set in pgbasenv.conf to control this timout. By default it is 5 sec.
 
-### v1.4
+## v1.4
 
 * Added support of SUSE Linux.
 * Other minor changes.
 
-### v1.3
+## v1.3
 
 * `$PGBASENV_BASE/scripts` was introduced to store the user scripts and inject them into psql. The list of the scripts will be available in psql under `:scripts` variable. Each script can be executed by enetering its own variable name. It is possible to define on which PostgreSQL version the particular script will be visible. Check corresponding section in main README.md file for details.
 * To prevent *pgclustertab* and *pghometab* corruption during simultaneous execution, operations will be executed over `flock` utility. It will guarantee a sequential access to those files and  `pgbasenv.sh` execution.