pgsql: Handle DROP DATABASE getting interrupted

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Handle DROP DATABASE getting interrupted
Date: 2023-07-13 20:29:40
Message-ID: E1qK2wW-000DmO-3K@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Handle DROP DATABASE getting interrupted

Until now, when DROP DATABASE got interrupted in the wrong moment, the removal
of the pg_database row would also roll back, even though some irreversible
steps have already been taken. E.g. DropDatabaseBuffers() might have thrown
out dirty buffers, or files could have been unlinked. But we continued to
allow connections to such a corrupted database.

To fix this, mark databases invalid with an in-place update, just before
starting to perform irreversible steps. As we can't add a new column in the
back branches, we use pg_database.datconnlimit = -2 for this purpose.

An invalid database cannot be connected to anymore, but can still be
dropped.

Unfortunately we can't easily add output to psql's \l to indicate that some
database is invalid, it doesn't fit in any of the existing columns.

Add tests verifying that a interrupted DROP DATABASE is handled correctly in
the backend and in various tools.

Reported-by: Evgeny Morozov <postgresql3(at)realityexists(dot)net>
Author: Andres Freund <andres(at)anarazel(dot)de>
Reviewed-by: Daniel Gustafsson <daniel(at)yesql(dot)se>
Reviewed-by: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Discussion: https://postgr.es/m/20230509004637.cgvmfwrbht7xm7p6@awork3.anarazel.de
Discussion: https://postgr.es/m/20230314174521.74jl6ffqsee5mtug@awork3.anarazel.de
Backpatch: 11-, bug present in all supported versions

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/1c38e7ae17b68a78dcef6a81be9fcf05ba91b374

Modified Files
--------------
doc/src/sgml/catalogs.sgml | 3 +-
src/backend/commands/dbcommands.c | 102 +++++++++++++++---
src/backend/commands/vacuum.c | 14 +++
src/backend/postmaster/autovacuum.c | 12 +++
src/backend/utils/init/postinit.c | 10 ++
src/bin/pg_dump/pg_dumpall.c | 4 +-
src/bin/pg_dump/t/002_pg_dump.pl | 21 +++-
src/bin/scripts/clusterdb.c | 4 +-
src/bin/scripts/reindexdb.c | 4 +-
src/bin/scripts/t/011_clusterdb_all.pl | 15 ++-
src/bin/scripts/t/050_dropdb.pl | 11 +-
src/bin/scripts/t/091_reindexdb_all.pl | 15 ++-
src/bin/scripts/t/101_vacuumdb_all.pl | 15 ++-
src/bin/scripts/vacuumdb.c | 2 +-
src/include/catalog/pg_database.h | 21 +++-
src/test/recovery/t/037_invalid_database.pl | 157 ++++++++++++++++++++++++++++
16 files changed, 383 insertions(+), 27 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2023-07-14 00:02:15 pgsql: Remove double quotes from the second column of wait_event_names.
Previous Message Tom Lane 2023-07-13 17:08:54 pgsql: Remove unnecessary pfree() in g_intbig_compress().