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 05:55:54
Message-ID: CAA4eK1JPd=fkKAgSM=4ELpdeam9oyN-8UkW1VKPNGRUREEERtw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, May 7, 2019 at 10:03 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Tue, May 7, 2019 at 9:51 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> > I'm just worried that that's an untested scenario.
> >
>
> I can test it. Basically, without revert of the patch, I can create a
> table with a few records (so as to ensure that there is no FSM). And
> then revert the patch and upgrade the database and perform few dml
> operations on that table and see what happens?
>

I have tested this both with and without an upgrade. This tests that
an existing v12 DB (with some missing FSM files) works with the
updated backend and the same works even if we do upgrade. If anyone
else can think of some other scenario's, please let me know.

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2019-05-07 09:08:06 Re: pgsql: docs: fist draft version of the PG 12 release notes
Previous Message Michael Paquier 2019-05-07 05:22:03 pgsql: Remove some code related to 7.3 and older servers from tools of