On Fri, Feb 17, 2006 at 08:23:40AM -0500, Ron wrote: > >For this mapping, you need a full table sort. > One physical IO pass should be all that's needed. However, let's > pretend you are correct and that we do need to sort the table to get > the key mapping. Even so, we would only need to do it =once= and > then we would be able to use and incrementally update the results > forever afterward. Even under this assumption, one external sort to > save all subsequent such sorts seems well worth it. > > IOW, even if I'm wrong about the initial cost to do this; it is still > worth doing ;-) I think you're talking about something different here. You're thinking of having the whole table sorted and when you add a new value you add it in such a way to keep it sorted. The problem is, what do you sort it by? If you've sorted the table by col1, then when the user does ORDER BY col2 it's useless. Indeed, this is what btrees do, you store the order of the table seperate from the data. And you can store multiple orders. But even then, when someone does ORDER BY lower(col1), it's still useless. And you're right, we still need to do the single mass sort in the beginning, which is precisely what we're trying to optimise here. > ??? You do not need to resort already ordered data to insert a new > element into it such that the data stays ordered! Once we have done > the key ordering operation once, we should not ever need to do it > again on the original data. Else most sorting algorithms wouldn't work ;-) We already do this with btree indexes. I'm not sure what you are proposing that improves on that. Have a nice day, -- Martijn van Oosterhout <kleptog@xxxxxxxxx> http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them.
Attachment:
signature.asc
Description: Digital signature
