On Fri, Apr 21, 2023 at 10:56 AM Aleksander Alekseev <aleksan...@timescale.com> wrote: > > Assuming this is the case perhaps we can reduce the scenario and > > consider this simpler one: > > > > 1. The table is truncated > > 2. The DBMS is killed before making a checkpoint > > 3. We are in recovery and presumably see a pair of 0.5 Gb segments > > > > Or can't we? > > Oh, I see. If the process will be killed this perhaps is not going to > happen. Whether this can happen if we pull the plug from the machine > is probably a design implementation of the particular filesystem and > whether it's journaled.
Right. I mentioned that scenario in the original email: "Furthermore, I think that the problem could arise without performing a backup at all: say that the server crashes on the OS level in mid-truncation, and the truncation of segment 0 reaches disk but the removal of segment 1 does not." -- Robert Haas EDB: http://www.enterprisedb.com