| From: | John Naylor <john(dot)naylor(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Unhappy about API changes in the no-fsm-for-small-rels patch |
| Date: | 2019-05-01 05:19:14 |
| Message-ID: | CACPNZCtoaLgCRG8JgXUJTFtMGTbEuZvbP_=HsXCwbZaim0XRCg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 1, 2019 at 11:43 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Tue, Apr 30, 2019 at 7:52 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> > but that seems correct.
> > Sounds better than keeping outdated entries indicating no-space-available.
>
> Agreed, but as mentioned in one of the above emails, I am also bit
> scared that it should not lead to many invalidation messages for small
> relations, so may be we should send the invalidation message only when
> the entire page is empty.
One way would be to send the inval if the new free space is greater
than some percentage of BLCKSZ.
--
John Naylor https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arthur Zakirov | 2019-05-01 07:05:44 | Re: [PATCH v4] Add \warn to psql |
| Previous Message | Tom Lane | 2019-05-01 04:43:34 | Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6 |