From 95f806e79102466c651f87cb2540c26b2eb3dd1a Mon Sep 17 00:00:00 2001 From: Rich Turner <7072278+richturner@users.noreply.github.com> Date: Mon, 18 May 2026 17:09:14 +0100 Subject: [PATCH] Cleanup of now obsolete variables --- README.md | 7 ------- or-entrypoint.sh | 3 +-- 2 files changed, 1 insertion(+), 9 deletions(-) diff --git a/README.md b/README.md index 0ee4ec2..aa074d9 100644 --- a/README.md +++ b/README.md @@ -11,13 +11,6 @@ POSTGIS and TimescaleDB (inc. toolkit for hyperfunctions) image built for amd64 `OR_DISABLE_AUTO_UPGRADE=true` - Auto upgrade of timescaleDB extension when a new version is available in the container; can be disabled using `OR_DISABLE_AUTO_UPGRADE=true` -- OR_DISABLE_REINDEX env variable with associated scripts to determine if a REINDEX of the entire DB should be carried - out at first startup with existing DB (checks whether or not `$PGDATA/OR_REINDEX_COUNTER.$OR_REINDEX_COUNTER` exists). - This is used when a collation change has occurred (glibc version change, muslc <-> glibc) which can break the indexes; - migration can either be manually handled or auto handled depending on OR_DISABLE_REINDEX env variable value. - NOTE THAT A REINDEX CAN TAKE A LONG TIME DEPENDING ON THE SIZE OF THE DB! And startup will be delayed until completed. - This functionality is intended to simplify migration for basic users; advanced users with large DBs should take care of this - themselves. - **Slimmed images** using [slim toolkit](https://github.com/slimtoolkit/slim) to reduce image size by ~60% ## Local Development diff --git a/or-entrypoint.sh b/or-entrypoint.sh index 0d73a31..a592918 100755 --- a/or-entrypoint.sh +++ b/or-entrypoint.sh @@ -20,8 +20,7 @@ # ============================================================================== # THIS FILE IS FOR MIGRATION OF EXISTING DB TO TIMESCALEDB IMAGE AS TIMESCALE INIT SCRIPTS AREN'T RUN WHEN DB -# ALREADY EXISTS; IT ALSO DOES AN AUTOMATIC REINDEX OF THE DB WHEN OR_REINDEX_COUNTER CHANGES TO SIMPLIFY MIGRATIONS -# IT ALSO AUTOMATICALLY HANDLES UPGRADING OF DATABASE AND DURING MAJOR VERSION CHANGES +# ALREADY EXISTS; IT ALSO AUTOMATICALLY HANDLES UPGRADING OF DATABASE DURING MAJOR VERSION CHANGES # BASED ON: https://github.com/pgautoupgrade/docker-pgautoupgrade source /docker-entrypoint.sh