| From: | "Jack Douglas" <jack(at)douglastechnology(dot)co(dot)uk> |
|---|---|
| To: | "'Alvaro Herrera'" <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Martijn van Oosterhout'" <kleptog(at)svana(dot)org>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: new index type with clustering in mind. |
| Date: | 2014-12-10 20:23:31 |
| Message-ID: | 013701d014b7$2a683ef0$7f38bcd0$@douglastechnology.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> If the values are perfectly clustered, the index is optimal because you
scan the minimal set of pages.
That's the bit I'm particularly interested in, as my plan would be to keep
the pages well clustered: http://dba.stackexchange.com/a/66293/1396
Do you see any blocker preventing BRIN being used for a continuous
background re-clustering job (in parallel with or as part of vacuum),
similar to the mechanism I experimented with before? If not is this
something there might be support for adding to the TODO list?
Kindest regards
Jack
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2014-12-10 20:28:35 | Re: Speeding up an in-progress wraparound-preventing vacuum |
| Previous Message | Gabriel Sánchez Martínez | 2014-12-10 19:50:32 | Re: invalid memory alloc request size |