2017-06-16 17:06 GMT+03:00 Tom Lane <t...@sss.pgh.pa.us>: > Yuan Dong <doff...@hotmail.com> writes: >> ·¢¼þÈË: Andrew Borodin <boro...@octonica.com> >>> I think there is one more aspect of development: backward >>> compatibility: it's impossible to update all existing extensions. This >>> is not that major feature to ignore them. > >> I should still maintain original API of GiST after modification. > > To put a little context on that: we have always felt that it's okay > to require extension authors to make small adjustments when going to > a new major release.
Then maybe it worth to consider more general API advancement at once? Here's my wish list: 1. Choose subtree function as an alternative for penalty 2. Bulk load support 3. Better split framework: now many extensions peek two seeds and spread split candidates among them, some with subtle but noisy mistakes 4. Better way of key compares (this thread, actually) 5. Split in many portions Best regards, Andrey Borodin. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
