Re: Can't we give better table bloat stats easily?

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Can't we give better table bloat stats easily?
Date: 2019-08-26 15:30:13
Message-ID: CAMkU=1zJ0J3Trmp0wt+vauDD2fpjnnApRS7cDiEm16oFzCrwJQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 16, 2019 at 8:39 PM Greg Stark <stark(at)mit(dot)edu> wrote:

> Everywhere I've worked I've seen people struggle with table bloat. It's
> hard to even measure how much of it you have or where, let alone actually
> fix it.
>
> If you search online you'll find dozens of different queries estimating
> how much empty space are in your tables and indexes based on pg_stats
> statistics and suppositions about header lengths and padding and plugging
> them into formulas of varying credibility.
>

There is not much we can do to suppress bad advice that people post on
their own blogs. If wiki.postgresql.org is hosting bad advice, by all
means we should fix that.

> But isn't this all just silliiness these days? We could actually sum up
> the space recorded in the fsm and get a much more trustworthy number in
> milliseconds.
>

If you have bloat problems, then you probably have vacuuming problems. If
you have vacuuming problems, how much can you trust fsm anyway?

Cheers,

Jeff

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ibrar Ahmed 2019-08-26 15:45:02 Re: pg_upgrade: Error out on too many command-line arguments
Previous Message Andrew Dunstan 2019-08-26 15:13:30 Re: mingw32 floating point diff