| From: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Add visibility map information to pg_freespace. |
| Date: | 2013-06-14 08:44:15 |
| Message-ID: | 20130614.174415.66698858.horiguchi.kyotaro@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Helle,
I've added visibility map information to pg_freespace for my
utility.
This looks like this,
postgres=# select * from pg_freespace('t'::regclass);
blkno | avail | all_visible
-------+-------+-------------
0 | 7424 | t
1 | 7424 | t
2 | 7424 | t
3 | 7424 | t
4 | 7424 | t
5 | 7424 | t
6 | 7424 | t
7 | 7424 | t
...
What do you think about this?
regards,
--
Kyotaro Horiguchi
NTT Open Source Software Center
| Attachment | Content-Type | Size |
|---|---|---|
| vm_to_freespacemap_20130614.patch | text/x-patch | 3.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KONDO Mitsumasa | 2013-06-14 08:52:29 | Re: Improvement of checkpoint IO scheduler for stable transaction responses |
| Previous Message | Kyotaro HORIGUCHI | 2013-06-14 08:35:28 | Reduce maximum error in tuples estimation after vacuum. |