Re: base backup vs. concurrent truncation - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: base backup vs. concurrent truncation
Date
Msg-id CAJ7c6TO1uY_wdx7cuKe6kTHGXWc3HdoRztjw2Ew9R-1R_5htjw@mail.gmail.com
Whole thread Raw
In response to Re: base backup vs. concurrent truncation  (Aleksander Alekseev <aleksander@timescale.com>)
Responses Re: base backup vs. concurrent truncation
List pgsql-hackers
Hi again,

> 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.

Hm...

-- 
Best regards,
Aleksander Alekseev



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: base backup vs. concurrent truncation
Next
From: Robert Haas
Date:
Subject: Re: base backup vs. concurrent truncation