From e815d466f7b0075601866c56029aab0269b1e10b Mon Sep 17 00:00:00 2001 From: Dzeri96 <13813363+Dzeri96@users.noreply.github.com> Date: Mon, 12 Sep 2022 17:25:58 +0200 Subject: [PATCH 1/2] Added clarification for the case with plugins This would have saved me so much time. --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 9333103..5453ade 100644 --- a/README.md +++ b/README.md @@ -109,3 +109,8 @@ $ docker logs --tail 100 postgres-upgrade-testing $ # can now safely remove "$OLD" $ sudo rm -rf "$OLD" ``` +## Upgrading with plugins: +If your current postgres installation has plugins installed, for example [TimescaleDB](https://www.timescale.com/), you'll have to create a custom container that has the needed plugins installed in both the old and new version of Postgres. +Additionally, supplying an option to pre-load any required libraries in the upgrade process is needed (`"-c shared_preload_libraries=YOUR_PLUGIN"`). + +For a simple example with TimescaleDB, refer to [this comment](https://github.com/timescale/timescaledb/issues/2260#issuecomment-686786971). From 1121f2085bd5b7da35559454d867b4cfe35d2108 Mon Sep 17 00:00:00 2001 From: Dzeri96 <13813363+Dzeri96@users.noreply.github.com> Date: Tue, 13 Sep 2022 11:50:16 +0200 Subject: [PATCH 2/2] Changed wording from plugin to extension --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 5453ade..d6c0874 100644 --- a/README.md +++ b/README.md @@ -109,8 +109,8 @@ $ docker logs --tail 100 postgres-upgrade-testing $ # can now safely remove "$OLD" $ sudo rm -rf "$OLD" ``` -## Upgrading with plugins: -If your current postgres installation has plugins installed, for example [TimescaleDB](https://www.timescale.com/), you'll have to create a custom container that has the needed plugins installed in both the old and new version of Postgres. +## Upgrading with extensions: +If your current postgres installation has extensions installed, for example [TimescaleDB](https://www.timescale.com/), you'll have to create a custom container that has the needed extensions installed in both the old and new version of Postgres. Additionally, supplying an option to pre-load any required libraries in the upgrade process is needed (`"-c shared_preload_libraries=YOUR_PLUGIN"`). For a simple example with TimescaleDB, refer to [this comment](https://github.com/timescale/timescaledb/issues/2260#issuecomment-686786971).