| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | When a GiST page is split during index build, it might not have a buffer. | Heikki Linnakangas | 2012-03-02 |
| | | | | | | | | | | | | | | Previously it was thought that it's impossible as the code stands, because insertions create buffers as tuples are cascaded downwards, and index split also creaters buffers eagerly for all halves. But the example from Jay Levitt demonstrates that it can happen, when the root page is split. It's in fact OK if the buffer doesn't exist, so we just need to remove the sanity check. In fact, we've been discussing the possibility of destroying empty buffers to conserve memory, which would render the sanity check completely useless anyway. Fix by Alexander Korotkov | ||
| * | Update copyright notices for year 2012. | Bruce Momjian | 2012-01-01 |
| | | |||
| * | Buffering GiST index build algorithm. | Heikki Linnakangas | 2011-09-08 |
| When building a GiST index that doesn't fit in cache, buffers are attached to some internal nodes in the index. This speeds up the build by avoiding random I/O that would otherwise be needed to traverse all the way down the tree to the find right leaf page for tuple. Alexander Korotkov | |||
 |
index : postgresql | |
| postgresql mirror |
| aboutsummaryrefslogtreecommitdiff |