Re: Freeze avoidance of very large table.

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Subject: Re: Freeze avoidance of very large table.
Date: 2015-08-19 23:16:38
Message-ID: 55D50E56.4020400@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/19/15 2:56 AM, Masahiko Sawada wrote:
> The currently regression test for VM is that we just compare between
> the total number of all-visible and all-frozen in VM before and after
> VACUUM, and don't check particular a bit in VM.
> we could substitute it to the ANALYZE command with enough sampling
> number and checking pg_class.relallvisible and pg_class.relallfrozen.

I think this is another indication that we need more than just pg_regress...

> So another way is that diagnostic function for VM is put into
> something contrib (pg_freespacemap or pageinspect), and if we want to
> use such function in production, we can install such extension as in
> the past.

pg_buffercache is very useful as a performance monitoring tool, and I
view being able to pull statistics about the VM and FM the same way. I'd
like to see us providing more performance information by default, not less.

I think things like pageinspect are very different; I really can't see
any use for those beyond debugging (and debugging by an expert at that).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-08-19 23:20:40 Re: proposal: function parse_ident
Previous Message Tom Lane 2015-08-19 22:42:16 Re: Mention column name in error messages