Re: pgsql: Revert "Avoid the creation of the free space map for small heap

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Amit Kapila <akapila(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Revert "Avoid the creation of the free space map for small heap
Date: 2019-05-07 04:18:15
Message-ID: CAA4eK1+VO8ef3krzaycw7f382yc=3sT5UxLbCgMt3v3EXZVL=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, May 7, 2019 at 9:44 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Amit Kapila <akapila(at)postgresql(dot)org> writes:
> > Revert "Avoid the creation of the free space map for small heap relations".
>
> Shouldn't there be a catversion bump in this? I doubt that an existing
> v12 DB (with some missing FSM files) is going to work with the updated
> backend.
>

Won't the next vacuum run will create the FSM? There is some
performance loss, but shouldn't be big.

> Also, will pg_upgrade work across that boundary?
>

I haven't tried it. What is your worry?

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2019-05-07 04:21:04 Re: pgsql: Revert "Avoid the creation of the free space map for small heap
Previous Message Amit Kapila 2019-05-07 04:14:54 Re: pgsql: docs: fist draft version of the PG 12 release notes