Re: Why copy_relation_data only use wal whenWALarchiving is enabled - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Why copy_relation_data only use wal whenWALarchiving is enabled
Date
Msg-id 471615E9.4040402@enterprisedb.com
Whole thread Raw
In response to Re: Why copy_relation_data only use wal when WALarchiving is enabled  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Why copy_relation_data only use wal whenWALarchiving is enabled
List pgsql-hackers
Simon Riggs wrote:
> If you've got a better problem statement it would be good to get that
> right first before we discuss solutions.

Reusing a relfilenode of a deleted relation, before next checkpoint
following the commit of the deleting transaction, for an operation that
doesn't WAL log the contents of the new relation, leads to data loss on
recovery.

Or

Performing non-WAL logged operations on a relation file leads to a
truncated file on recovery, if the relfilenode of that file used to
belong to a relation that was dropped after the last checkpoint.

Happy?

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: Why copy_relation_data only use wal when WALarchiving is enabled
Next
From: Heikki Linnakangas
Date:
Subject: Re: Why copy_relation_data only use wal when WALarchiving is enabled