Re: WIP: Avoid creation of the free space map for small tables - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: WIP: Avoid creation of the free space map for small tables
Date
Msg-id CAH2-Wzk6CmEp08T2zHYqO6huy-yAwMszrtEU2vOzOgsH8Wz4yA@mail.gmail.com
Whole thread Raw
In response to Re: WIP: Avoid creation of the free space map for small tables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: WIP: Avoid creation of the free space map for small tables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Fri, Feb 22, 2019 at 8:04 AM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> Wow, there's a lot less tests failing there than I thought there would
> be.  That increases hope that we can someday have them pass.  +1 on not
> making things worse.
>
> I think the crash in the amcheck test should be studied, one way or
> another; CCing Peter.

I built Postgres with "--with-blocksize=16" and "--with-blocksize=32",
and tested amcheck with both builds. All tests passed.

I have a hard time imagining what the problem could be here. If there
was a problem with amcheck relying on there being an 8KiB block size
specifically, then it would almost certainly have been there since the
initial commit from March 2017. Not much has changed since then, and
the crash that Amit reported occurs at the earliest possible point.

I find it suspicious that there is another crash in pageinspect's
brin_page_items(), since like amcheck, pageinspect is a contrib module
that relies on BLCKSZ when allocating a local temp buffer.

-- 
Peter Geoghegan


pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Refactoring the checkpointer's fsync request queue
Next
From: Andres Freund
Date:
Subject: Re: Refactoring the checkpointer's fsync request queue