| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Emre Hasegeli <emre(at)hasegeli(dot)com> |
| Subject: | Re: Better tracking of free space during SP-GiST index build |
| Date: | 2016-09-28 17:49:59 |
| Message-ID: | CA+TgmobzX2eu3WhWcfMj3RXAjCrn5GGHhn79XZcZSHA1D6X3OA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 22, 2016 at 1:37 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> OK, I'll think about how to do that more efficiently. The smaller
> incremental improvement isn't surprising, because in this example the
> index would still be 90-something MB if it had no free space at all,
> so there's going to be decreasing returns from any additional work
> to avoid wasted free space. But if we can do it cheaply, this does
> suggest that using pages in order by free space is of value.
Tom, are you planning to do something about this patch yet this
CommitFest, or leave it until later?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-09-28 17:57:03 | CommitFest wrap-up |
| Previous Message | Robert Haas | 2016-09-28 17:48:56 | Re: Better tracking of free space during SP-GiST index build |