Re: The Free Space Map: Problems and Opportunities

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jan Wieck <jan(at)wi3ck(dot)info>, Gregory Smith <gregsmithpgsql(at)gmail(dot)com>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: The Free Space Map: Problems and Opportunities
Date: 2021-08-20 19:20:16
Message-ID: CA+TgmoZWh9pWwK5bgjJk3KqqsjMtK9oekqjTs0P1t4YJHcahQA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 20, 2021 at 3:13 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> In short: yeah, this "closed vs open" page business more or less
> necessitates tightening things up here. Though this new requirement
> seems to have always been a good idea. Just because we can lean on
> VACUUM like this (an option that other DB systems don't have) doesn't
> mean that we should do so.

That's all true, but it's not what I was talking about.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-08-20 19:25:22 Re: Use extended statistics to estimate (Var op Var) clauses
Previous Message Peter Geoghegan 2021-08-20 19:12:47 Re: The Free Space Map: Problems and Opportunities