kkimurak/sameersbn-postgresql repository overview

⁠kkimurak/sameersbn-postgresql

⁠overview

This is a fork of sameersbn/postgresql⁠ aiming to provide regular builds and to support sameersbn/gitlab⁠ as upstream repository is not updated since last release of 15-20230628.
Changes should be kept to a minimum and pull requests should be sent to upstream whenever appropriate.

Feel free to submit feedback to github issue⁠. Make sure that you have check to see if there is any implementation work already underway in pull request⁠.

Repository: https://github.com/kkimurak/docker-postgresql⁠
(forked from https://github.com/sameersbn/docker-postgresql⁠)

Build / push around 17:30 ~ 19:00 on every Thursday (JST: UTC+0900)

Initially, I created merge requests to merge changes into each major version branch, but this became tedious.
So I created a build script that automatically merges develop branch⁠ before building each version. Unless explicitly stated otherwise, changes made to develop are automatically applied to each image.

⁠major notes

• 2026-08-17: 18.6, 17.11, 16.15, 15.19 and 14.24 will be released on next regular release (planned: 2026-08-20).
  Note that 18.5 is not shipped due to regression on upstream. See release news⁠
• 2026-06-04: Introduced following change:
  • Fix typo in README (missing trailing "S" of PG_ENABLE_CHECKSUMS) (kkimurak/docker-postgresql#22⁠)
• 2026-04-16: Introduced following change:
  • Redirect output of pg_ctl to file in PG_LOGDIR instead of /dev/null (kkimurak/docker-postgresql#21⁠)
    Logs during user / database / replication user creationcan be seen in /var/log/postgresql/postgresql-{major-version}-internal.log.
    Since the log directory is not specified as a volume, you will need to persist it manually if necessary. Thank you for report and suggestion @th-2021⁠
• 2026-04-09: Introduced following change:
  • Issue/18 support checksum feature (kkimurak/docker-postgresql#19⁠)
    Now you can use env var PG_ENABLE_CHECKSUMS (true or false) to set checksums status.
    Automatic upgrade also handle checksums status on upgrade source and temporarily updates on destination cluster
• 2026-02-19: Introduced following changes:
  • 12 or later: Replace deprecated recovery.conf by standby.signal (kkimurak/docker-postgresql#15⁠)
  • 9.6 or later: some minor changes (kkimurak/docker-postgresql#16⁠)
  • 14 or later: Rename wal_keep_segments to wal_keep_size and set greater value (kkimurak/docker-postgresql#17⁠)
• 2026-01-22: Introduced following feature:
  • Add unified access to postgresql.conf via prefixed environment variables
    Now you can set all of parameters in postgresql.conf by setting environment variable prefixed with PG_PARAM_.
    See kkimurak/docker-postgresql#14⁠
• 2025-11-18: Support for postgresql 13.x has ended (2025-11-13: See https://www.postgresql.org/about/news/postgresql-181-177-1611-1515-1420-and-1323-released-3171/⁠).
  Build 20251120 will be the final release that includes 13.x.
• 2025-11-06: Base image is upgraded from ubuntu:jammy (22.04) to ubuntu:noble (24.04)
• 2025-09-19: The regular release on 2025-09-25 is expected to support major version :18, but this will be the release date of postgresql-18 itself and may be delayed for testing purposes.
  • 2025-09-25 18:47:00 +0900 (JST): Regular push excluding major version 18
  • 2025-09-26 00:11:00 +0900 (JST): push 18, 18.0, 18.0-1, 18-20250925
• 2025-07-24: Introduced following changes:
  • Fix IFS parsing (kkimurak/docker-postgresql#11⁠)
    Because functions that modify IFS were nested and the variable IFS_ORG used to store the original IFS was a global variable, the contents of the original IFS were lost. Thank you for report and fix @Re4zOon⁠
• 2025-07-17: Introduced following changes:
  • Replace awk -F based csv iteration by IFS + built-in for loop (kkimurak/docker-postgresql#9⁠)
    Now DB_NAME and DB_EXTENSION are not splitted whitespace or something unintendently but only by comma. User can include options such as CASCADE to DB_EXTENSION.
  • Add parameter DB_USER_IS_DB_OWNER (boolean) (kkimurak/docker-postgresql#10⁠)
    DB_USER can be an owner of database listed in DB_NAME by setting DB_USER_IS_DB_OWNER to true.
• 2025-05-18: Illegular push 15, 16 and 17 to support sameersbn/gitlab:18
  • Now the DB_USER have ALL grant to public schema in database DB_NAME.
    See kkimurak/docker-postgresql#1⁠, kkimurak/docker-postgresql#5⁠ and sameersbn/docker-gitlab#3107⁠
• 2025-05-01: First regular push, 13, 14, 15, 16 and 17
• 2025-04-24: First push, 15 and 16

⁠delay notice

• 2026-08-13: 40 minutes later than usual due to the Obon holiday in Japan
• 2026-07-30: 30 minutes later than usual to check "pushed tag not visible" issue⁠ on docker hub
• 2026-03-05: (planned) 5~6 hours later than usual for business trip
  • actual: 3 hours later than usual (21:47 +0900)
• 2026-02-05: 15 minutes later than usual
• 2026-01-02: 1 day and 3 hours later than usual, happy new year
• 2025-11-06: 30 minutes later than usual for base image upgrade
• 2025-10-16: 5 hours later than usual
• 2025-10-02: 20 minutes later than usual
• 2025-09-06: Two days later than usual due to a business trip and a typhoon
• 2025-08-16: Two days later than usual due to the Obon holiday in Japan
• 2025-08-07: An hour later than usual (19:50:00 JST)
• 2025-06-05: Regular push 3-4 hours later than usual (22:45:00 JST)
• 2025-05-29: The build for this week are suspended as archive.ubuntu.com is temporally in unstable state.
  See https://status.canonical.com/⁠
  • 2025-05-30: Regular push with 1 day delay

⁠version table

There are following variations for image tag:

• {MAJOR}-{date_YYYYMMDD}
• {MAJOR}
• {MAJOR}.{MINOR}
• {MAJOR}.{MINOR}-{PATCH}

For example, There are :18, :18.1, :18.1-1 (mutable - overwritten if newer image with same version pushed) and :18-20251211 (mostly immutable)

You can check Dockerfile by clicking each major versions.

⁠team

maintainer: kkimurak (https://github.com/kkimurak⁠)