From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Could ANALYZE estimate bloat? |
Date: | 2013-09-20 21:17:03 |
Message-ID: | 20130920211703.GK2706@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Josh,
* Josh Berkus (josh(at)agliodbs(dot)com) wrote:
> I've been tinkering with a number of table bloat checks, and it occurred
> to me that the problm is that these are all approximations based on
> overall gross statistics, and as such highly inaccurate.
Greg Smith and I discussed some improvements around this area @Open.
I'd suggest you talk with him about the ideas that he has.
> It seems like would could have ANALYZE, while sampling from the table,
> also check the amount of dead space per page and use that as an estimate
> of the % of dead space overall. We'd still need something else for
> indexes, but this seems like it would be a good start.
>
> No?
Err, I thought that was one of the things like ANALYZE *did* collect
through the 'live tuples' number?
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-09-20 21:18:05 | Re: SSL renegotiation |
Previous Message | Peter Geoghegan | 2013-09-20 21:15:23 | Re: logical changeset generation v6 |