From b7f9c762a8e10a64866309b64b785a4496bcd194 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 7 Nov 2022 13:02:24 -0500 Subject: [PATCH] Last-minute updates for release notes. --- doc/src/sgml/release-15.sgml | 42 ++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) diff --git a/doc/src/sgml/release-15.sgml b/doc/src/sgml/release-15.sgml index 3019d6c61f2..78aa7c1bb80 100644 --- a/doc/src/sgml/release-15.sgml +++ b/doc/src/sgml/release-15.sgml @@ -21,6 +21,11 @@ A dump/restore is not required for those running 15.X. + + + However, if you regularly create and drop tables exceeding 1GB, + see the first changelog entry below. + @@ -31,6 +36,43 @@ + + Fix failure to remove non-first segments of large tables + (Tom Lane) + + + + PostgreSQL splits large tables into + multiple files (normally with 1GB per file). The logic for dropping + a table was broken and would miss removing all but the first such + file, in two cases: drops of temporary tables and WAL replay of + drops of regular tables. Applications that routinely create + multi-gigabyte temporary tables could suffer significant disk space + leakage. + + + + Orphaned temporary-table files are removed during postmaster start, + so the mere act of updating to 15.1 is sufficient to clear any + leaked temporary-table storage. However, if you suffered any + database crashes while using 15.0, and there might have been + large tables dropped just before such crashes, it's advisable + to check the database directories for files named according to the + pattern + NNNN.NN. + If there is no matching file named + just NNNN (without + the .NN suffix), these + files should be removed manually. + + + + +