| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Satoshi Nagayasu <snaga(at)uptime(dot)jp> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add visibility map information to pg_freespace. |
| Date: | 2013-06-21 15:34:43 |
| Message-ID: | CA+TgmoYL38idf+HE-BHDwxoxk_gp6eb1XERmb_4US7MNVkZtJA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 19, 2013 at 11:26 PM, Satoshi Nagayasu <snaga(at)uptime(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cédric Villemain | 2013-06-21 16:02:35 | Re: Why can't I use windowing functions over ordered aggregates? |
| Previous Message | Jeff Davis | 2013-06-21 15:33:26 | Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls |