Merge pull request #253158 from GennadNY/gennadk900

Update concepts-certificate-rotation.md

Author: prmerger-automator[bot]

articles/postgresql/flexible-server/concepts-extensions.md

@@ -563,7 +563,9 @@ This is part of contrib and it is very easy to install this extension.
 CREATE EXTENSION pg_buffercache;
 ```
 
+## Extensions and Major Version Upgrade
 
+Azure Database for PostgreSQL Flexible Server Postgres has  introduced [in-place major version upgrade](./concepts-major-version-upgrade.md#overview) feature that performs an in-place upgrade of the Postgres server with just a click. In-place major version upgrade simplifies Postgres upgrade process minimizing the disruption to users and applications accessing the server. In-place major version upgrade doesn't support certain extensions and there are some limitations to upgrading certain extensions. The extensions **Timescaledb**, **pgaudit**, **dblink**, **orafce** and **postgres_fdw** are unsupported for all PostgreSQL versions when using [in-place majpr version update feature](./concepts-major-version-upgrade.md#overview).
 
 
 ## Next steps

articles/postgresql/single-server/concepts-certificate-rotation.md

@@ -152,7 +152,7 @@ No. There's no action needed if your certificate file already has the **DigiCert
 There are many tools that you can use. For example, DigiCert has a handy [tool](https://www.digicert.com/help/) that  shows you the certificate chain of any server name. (This tool works with publicly accessible server; it cannot connect to server that is contained in a virtual network (VNET)). 
 Another tool you can use is OpenSSL in the command line, you can use this syntax to check certificates:
 ```bash
-openssl s_client -showcerts -connect <your-postgresql-server-name>:443
+openssl s_client -starttls postgres -showcerts -connect <your-postgresql-server-name>:5432
 ```
 
 ### 14. What if I have further questions?