{"push_id":2974653666,"size":1,"distinct_size":1,"ref":"refs/heads/fast-drop-index","head":"2d41adf6ae347f52b25ef493f93c4148b01b9b4a","before":"7034e6da5f114750e014094ee301941219523f08","commits":[{"sha":"2d41adf6ae347f52b25ef493f93c4148b01b9b4a","author":{"name":"Erik Trinh","email":"c195b508e6f0c57aeafdb5e96947e2b79e6a4b40@cockroachlabs.com"},"message":"sql: use ClearRange for index truncation\n\nThis change makes the deletion of index data use the ClearRange batch\nrequest. DROP INDEX schema changes in the same transaction as the one\nwhich created the table still uses the slower DelRange because\nClearRange cannot be run inside a transaction and will remove write\nintents of the index keys which have not been resolved in the\ntransaction.\n\nThis deletion of index data happens once the GC TTL period has passed\nand it is safe to remove all the data. See PR #30566 for which delays\nthis data deletion.\n\nFixes #20696.\n\nRelease note (performance improvement): Deletion of index data is faster.","distinct":true,"url":"https://api.github.com/repos/eriktrinh/cockroach/commits/2d41adf6ae347f52b25ef493f93c4148b01b9b4a"}]}
{"actor":{"display_login":"eriktrinh"}}