From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Noah Bergbauer <noah(at)statshelix(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Preventing free space from being reused |
Date: | 2021-02-12 21:43:13 |
Message-ID: | 1607744.1613166193@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Noah Bergbauer <noah(at)statshelix(dot)com> writes:
> I am working on a project where I do not want Postgres to reuse free space
> in old pages (see
> https://www.postgresql.org/message-id/flat/CABjy%2BRhbFu_Hs8ZEiOzaPaJSGB9jqFF0gDU5gtwCLiurG3NLjQ%40mail.gmail.com
> for details). I found that the HEAP_INSERT_SKIP_FSM flag accomplishes this.
> For a long-term solution I see two options:
> 1. Introduce a reloption for this.
> 2. Implement it as a custom table access method in an extension.
TBH, I can't believe that this is actually a good idea. If we introduce
a reloption that does that, we'll just be getting users complaining about
table bloat ... but probably only after they get to a state where it's
going to be horribly painful to get out of.
(My reaction to your previous thread was that it was simply a question
of blindly insisting on using BRIN indexes for a case that they're quite
badly adapted to. The better answer is to not use BRIN.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Bergbauer | 2021-02-12 22:21:28 | Re: Preventing free space from being reused |
Previous Message | Thomas Munro | 2021-02-12 21:41:16 | Experimenting with redo batching |