Simon Riggs wrote >> Can you CLUSTER >> against a minmax index? > > Not in this release, at least in my understanding. It's not yet > possible to do an ordered fetch, so the cluster scan probably won't > work.
As per the patch I helped writing, CLUSTER should use the sequential heap scan+sort when "it makes sense". So I think that if the index is not able to do an ordered fetch, CLUSTER should fall back to scan+sort automatically (which is what you want in a large table anyway). Obviously, that should be tested. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Fast-insertion-indexes-why-no-developments-tp5776227p5778171.html Sent from the PostgreSQL - hackers mailing list archive at Nabble.com. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
