docker-images/postgres
docker-images/postgres
1
0
Fork 0
mirror of https://github.com/docker-library/postgres.git synced 2025-04-19 11:42:18 +03:00
Code

Remove inaccurate references to corruption, remove SEGTERM suggestion… (#1303)

Browse Source 
* Remove inaccurate references to corruption, remove SEGTERM suggestion, update information links to current docs. Postgres is carefully designed such that data is not corrupted on crashes or unclean shutdowns - the main tradeoff is that WAL replay is needed on startup. In practice, SIGTERM can cause unexpected long delays to shutdowns - often during maintenance windows - so best not to actively suggest this. The links back to official Postgres documentation seem sufficient.
This commit is contained in:
Jeremy Schneider 2025-01-09 09:56:49 -08:00 committed by GitHub
parent cb049360d9
commit 32b6fcdda7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
26 changed files with 130 additions and 286 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
12/alpine3.20/Dockerfile generated
View File

@ -203,18 +203,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -224,10 +218,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
12/alpine3.21/Dockerfile generated
View File

@ -203,18 +203,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -224,10 +218,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
12/bookworm/Dockerfile generated
View File

@ -194,18 +194,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -215,10 +209,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
12/bullseye/Dockerfile generated
View File

@ -194,18 +194,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -215,10 +209,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
13/alpine3.20/Dockerfile generated
View File

@ -203,18 +203,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -224,10 +218,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
13/alpine3.21/Dockerfile generated
View File

@ -203,18 +203,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -224,10 +218,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
13/bookworm/Dockerfile generated
View File

@ -196,18 +196,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -217,10 +211,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
13/bullseye/Dockerfile generated
View File

@ -196,18 +196,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -217,10 +211,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
14/alpine3.20/Dockerfile generated
View File

@ -206,18 +206,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -227,10 +221,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
14/alpine3.21/Dockerfile generated
View File

@ -206,18 +206,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -227,10 +221,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
14/bookworm/Dockerfile generated
View File

@ -194,18 +194,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -215,10 +209,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
14/bullseye/Dockerfile generated
View File

@ -194,18 +194,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -215,10 +209,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
15/alpine3.20/Dockerfile generated
View File

@ -209,18 +209,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -230,10 +224,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
15/alpine3.21/Dockerfile generated
View File

@ -209,18 +209,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -230,10 +224,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
15/bookworm/Dockerfile generated
View File

@ -194,18 +194,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -215,10 +209,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
15/bullseye/Dockerfile generated
View File

@ -194,18 +194,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -215,10 +209,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
16/alpine3.20/Dockerfile generated
View File

@ -208,18 +208,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -229,10 +223,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
16/alpine3.21/Dockerfile generated
View File

@ -208,18 +208,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -229,10 +223,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
16/bookworm/Dockerfile generated
View File

@ -194,18 +194,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -215,10 +209,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
16/bullseye/Dockerfile generated
View File

@ -194,18 +194,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -215,10 +209,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
17/alpine3.20/Dockerfile generated
View File

@ -206,18 +206,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -227,10 +221,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
17/alpine3.21/Dockerfile generated
View File

@ -206,18 +206,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -227,10 +221,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
17/bookworm/Dockerfile generated
View File

@ -194,18 +194,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -215,10 +209,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
17/bullseye/Dockerfile generated
View File

@ -194,18 +194,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -215,10 +209,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
Dockerfile-alpine.template
View File

@ -232,18 +232,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -253,10 +247,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432

16
Dockerfile-debian.template
View File

@ -192,18 +192,12 @@ ENTRYPOINT ["docker-entrypoint.sh"]
# We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL # We set the default STOPSIGNAL to SIGINT, which corresponds to what PostgreSQL
# calls "Fast Shutdown mode" wherein new connections are disallowed and any # calls "Fast Shutdown mode" wherein new connections are disallowed and any
# in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and # in-progress transactions are aborted, allowing PostgreSQL to stop cleanly and
# flush tables to disk, which is the best compromise available to avoid data # flush tables to disk.
# corruption.
# #
# Users who know their applications do not keep open long-lived idle connections # See https://www.postgresql.org/docs/current/server-shutdown.html for more details
# may way to use a value of SIGTERM instead, which corresponds to "Smart
# Shutdown mode" in which any existing sessions are allowed to finish and the
# server stops when all sessions are terminated.
#
# See https://www.postgresql.org/docs/12/server-shutdown.html for more details
# about available PostgreSQL server shutdown signals. # about available PostgreSQL server shutdown signals.
# #
# See also https://www.postgresql.org/docs/12/server-start.html for further # See also https://www.postgresql.org/docs/current/server-start.html for further
# justification of this as the default value, namely that the example (and # justification of this as the default value, namely that the example (and
# shipped) systemd service files use the "Fast Shutdown mode" for service # shipped) systemd service files use the "Fast Shutdown mode" for service
# termination. # termination.
@ -213,10 +207,10 @@ STOPSIGNAL SIGINT
# An additional setting that is recommended for all users regardless of this # An additional setting that is recommended for all users regardless of this
# value is the runtime "--stop-timeout" (or your orchestrator/runtime's # value is the runtime "--stop-timeout" (or your orchestrator/runtime's
# equivalent) for controlling how long to wait between sending the defined # equivalent) for controlling how long to wait between sending the defined
# STOPSIGNAL and sending SIGKILL (which is likely to cause data corruption). # STOPSIGNAL and sending SIGKILL.
# #
# The default in most runtimes (such as Docker) is 10 seconds, and the # The default in most runtimes (such as Docker) is 10 seconds, and the
# documentation at https://www.postgresql.org/docs/12/server-start.html notes # documentation at https://www.postgresql.org/docs/current/server-start.html notes
# that even 90 seconds may not be long enough in many instances. # that even 90 seconds may not be long enough in many instances.
EXPOSE 5432 EXPOSE 5432