Re: Unhappy about API changes in the no-fsm-for-small-rels patch

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: John Naylor <john(dot)naylor(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 19:21:24
Message-ID: 20190501192124.GA2159@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-May-01, Amit Kapila wrote:

> On Tue, Apr 30, 2019 at 7:52 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:

> > Hmm ... so, if vacuum runs and frees up any space from any of the pages,
> > then it should send out an invalidation -- it doesn't matter what the
> > FSM had, just that there is more free space now. That means every other
> > process will need to determine a fresh FSM,
>
> I think you intend to say the local space map because once FSM is
> created we will send invalidation and we won't further build relcache
> entry having local space map.

Yeah, I mean the map that records free space.

> > 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.

I don't think that's a concern, is it? You typically won't be running
multiple vacuums per second, or even multiple vacuums per minute.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-05-01 19:39:47 Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6
Previous Message Tom Lane 2019-05-01 19:13:12 Re: [HACKERS] Commits 8de72b and 5457a1 (COPY FREEZE)