Re: Add visibility map information to pg_freespace. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Add visibility map information to pg_freespace.
Date
Msg-id CA+TgmoYL38idf+HE-BHDwxoxk_gp6eb1XERmb_4US7MNVkZtJA@mail.gmail.com
Whole thread Raw
In response to Re: Add visibility map information to pg_freespace.  (Satoshi Nagayasu <snaga@uptime.jp>)
List pgsql-hackers
On Wed, Jun 19, 2013 at 11:26 PM, Satoshi Nagayasu <snaga@uptime.jp> wrote:
> - pageinspect provies several functions for debugging purpose.
> - pg_freespace provies a view for monitoring purpose.
> - pgstattuple provies several functions for collecting
>   specific table/index statistics.

I think we should be careful to think about upgrade considerations
when adding this functionality.  Bumping the module version number to
add new functions is less likely to break things for users than
changing the return value of an existing SRF.  Maybe that's too far
down in the weeds to worry about, but it's a thought - especially for
pg_freespace, where there's no real efficiency benefit to have the
same function look at the FSM and the VM anyway.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls
Next
From: Cédric Villemain
Date:
Subject: Re: Why can't I use windowing functions over ordered aggregates?