From: | Dawn Yu <boyyuxiao1987(at)gmail(dot)com> |
---|---|
To: | Rui DeSousa <rui(at)crazybean(dot)net> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: A Question about FPW and WAL |
Date: | 2023-04-11 05:53:26 |
Message-ID: | CALiuKDFRXcE77dm=c1gcsL12_DOw6zXSt-E3hk-wjen0a-7vSw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ok, thanks.
On Mon, 3 Apr 2023 at 22:30, Rui DeSousa <rui(at)crazybean(dot)net> wrote:
>
>
> On Apr 3, 2023, at 5:38 AM, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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.
>
From | Date | Subject | |
---|---|---|---|
Next Message | James Pang (chaolpan) | 2023-04-12 03:03:12 | attach partition to parent table with default partition accessexclusive |
Previous Message | Joseph Hammerman | 2023-04-11 03:52:46 | s3-fuse and tiered storage |