Re: PageGetFreeSpace() isn't quite the right thing for some of its callers

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Subject: Re: PageGetFreeSpace() isn't quite the right thing for some of its callers
Date: 2019-04-08 21:14:48
Message-ID: CAH2-Wz=o9+LgBOLVVfYaeXND4DCxuuwSDXJJ0Ejzu4NK7G0rgg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 8, 2019 at 2:10 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I'm not sure I understand what the problem is. We got to get the
> information for the fsm from somewhere? Are you arguing we should
> instead have it included as an explicit xlog record payload?

No. I am simply pointing out that PageGetFreeSpace() "should usually
only be used on index pages" according to its own comments. And yet
it's called for other stuff.

Maybe it's not that important in that one instance, but I find it
pretty distracting that PageGetFreeSpace() is intended for index AMs
that use conventional line pointers.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2019-04-08 22:10:57 Re: change password_encryption default to scram-sha-256?
Previous Message Andres Freund 2019-04-08 21:10:40 Re: PageGetFreeSpace() isn't quite the right thing for some of its callers