| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | masao(dot)fujii(at)gmail(dot)com, robertmhaas(at)gmail(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: the number of pending entries in GIN index with FASTUPDATE=on |
| Date: | 2012-12-05 08:08:38 |
| Message-ID: | 50BF0106.1000401@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28.11.2012 04:11, Kyotaro HORIGUCHI wrote:
>>> 3. pgstatginidex shows only version, pending_pages, and
>>> pendingtuples. Why don't you show the other properties such as
>>> entry pages, data pages, entries, and total pages as
>>> pgstatindex does?
>>
>> I didn't expose those because they are accurate as of last VACUUM.
>> But if you think they are useful, I don't object to expose them.
>
> Ok, my point was the apparent consistency of the functions. I
> don't have any distinct wish about this.
We can always add more fields later if there's a need.
> I'll mark this as Ready for Committer.
Thanks, committed.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2012-12-05 08:10:58 | Re: WIP: store additional info in GIN index |
| Previous Message | Pavel Stehule | 2012-12-05 08:06:22 | Re: why can't plpgsql return a row-expression? |