Re: using an end-of-recovery record in all cases - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: using an end-of-recovery record in all cases
Date
Msg-id CA+hUKGJwOf0bkadnHb=tFUrRo6Pai4EGeHM3DXeaUZu1HSUEKA@mail.gmail.com
Whole thread Raw
In response to Re: using an end-of-recovery record in all cases  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
On Thu, Apr 21, 2022 at 5:02 AM Nathan Bossart <nathandbossart@gmail.com> wrote:
> I do see the problem if we drop an existing relation, crash, reuse the
> filenode, and then crash again (all within the same checkpoint cycle).  The
> first recovery would remove the tombstone file, and the second recovery
> would wipe out the new relation's files.

Right, the double-crash case is what I was worrying about.  I'm not
sure, but it might even be more likely than usual that you'll reuse
the same relfilenode after the first crash, because the OID allocator
will start from the same value.



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: using an end-of-recovery record in all cases
Next
From: Stephen Frost
Date:
Subject: Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file