From: Rui DeSousa <rui@crazybean.net>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Dawn Yu <boyyuxiao1987@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: A Question about FPW and WAL
Date: Mon, 3 Apr 2023 10:30:11 -0400
Message-ID: <718AEDDD-FE66-4865-A362-0A7B760B5DF1@crazybean.net> (raw)
In-Reply-To: <942e247261151cddf5d57cf7797d6bf3c9b067a7.camel@cybertec.at>
References: <CALiuKDHL-5h4DWYKiCXpQHJ8UHEG7mKj38eJVGWeT=nf604bLQ@mail.gmail.com>
<942e247261151cddf5d57cf7797d6bf3c9b067a7.camel@cybertec.at>
> 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.=
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: rui@crazybean.net, laurenz.albe@cybertec.at, boyyuxiao1987@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: A Question about FPW and WAL
In-Reply-To: <718AEDDD-FE66-4865-A362-0A7B760B5DF1@crazybean.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox