Index only scan paving the way for "auto" clustered tables?
От | Royce Ausburn |
---|---|
Тема | Index only scan paving the way for "auto" clustered tables? |
Дата | |
Msg-id | 13A47B0B-97DB-4BBE-B071-07C68DBA750F@inomial.com обсуждение исходный текст |
Ответы |
Re: Index only scan paving the way for "auto" clustered tables?
|
Список | pgsql-hackers |
Hi all, I wonder, could the recent work on index only scans pave the way for auto clustered tables? Consider a wide, mostly inserttable with some subset of columns that I'd like to cluster on. I'm after locality of tuples that are very frequentlyfetched together, but not keen on the downtime for a cluster, nor the maintenance that it requires. Would it bea stretch to have an index that branches on the subset of "cluster" columns, but still stores all the columns, making ita covering index? Given that we can already index concurrently, such an index would not require downtime, and would beself maintaining. From my understanding of the index-only scan implementation, I suspect that such an index would effectivelygive locality, with some caveats… I'd expect the overhead of inserting in to such a table would be high, perhaps prohibitive. Perhaps better ways have beendiscussed. Stupid idea? --Royce
В списке pgsql-hackers по дате отправления: