Skip to content

Update ENVIRONMENT.rst to reflect nature of PGHOME, PGROOT and PGDATA#1192

Open
robinp wants to merge 1 commit intozalando:triggerfrom
robinp:patch-1
Open

Update ENVIRONMENT.rst to reflect nature of PGHOME, PGROOT and PGDATA#1192
robinp wants to merge 1 commit intozalando:triggerfrom
robinp:patch-1

Conversation

@robinp
Copy link
Copy Markdown

@robinp robinp commented Mar 20, 2026

@zalando-robot
Copy link
Copy Markdown

Cannot start a pipeline due to:

No accountable user for this pipeline: no Zalando employee associated to this GitHub username

Click on pipeline status check Details link below for more information.

@robinp
Copy link
Copy Markdown
Author

robinp commented Mar 25, 2026

Note: mildly unrelated, but PG_CONNECT_ADDRESS is missing from the enumeration completely. It is the "advertised address" towards peer Patroni-s/Spilo-s about where to connect to the primary for replication.

Comment thread ENVIRONMENT.rst
- **CLONE_TARGET_TIMELINE**: timeline id of the backup for restore, 'latest' by default.
- **CRONTAB**: anything that you want to run periodically as a cron job (empty by default)
- **PGROOT**: a directory where we put the pgdata (by default /home/postgres/pgroot). One may adjust it to point to the mount point of the persistent volume, such as EBS.
- **PGHOME**: filesystem path where to put PostgreSQL home directory (/home/postgres by default). Only docker-build-time env var!
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what do you mean by "docker-build-time env var"? this variable is also available at runtime.
Or your point is about this env var being not configurable at runtime?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants