Re: A Question about FPW and WAL - Mailing list pgsql-admin

From Rui DeSousa
Subject Re: A Question about FPW and WAL
Date
Msg-id 718AEDDD-FE66-4865-A362-0A7B760B5DF1@crazybean.net
Whole thread Raw
In response to Re: A Question about FPW and WAL  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: A Question about FPW and WAL  (Dawn Yu <boyyuxiao1987@gmail.com>)
List pgsql-admin


On Apr 3, 2023, at 5:38 AM, Laurenz Albe <laurenz.albe@cybertec.at> wrote:

By default, index full-page write is disabled. If the index is broken, you can
rebuild the index to solve it. Although the security of index data cannot be
guaranteed, this setting can greatly reduce the problem of storage space explosion
caused by wal write amplification.

I would feel funny about a parameter like that.

I agree. To allow for indexes to become corrupt by design would be a bad idea. Rebuilding indexes is a not a solution as some index rebuilds takes hours on very large tables. Dealing with identifying corrupted indexes and the issues caused by them would be a nightmare to deal with and not very ACID compliant.

pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: A Question about FPW and WAL
Next
From: Roland Che
Date:
Subject: ERROR: invalid memory alloc request size