On Wed, Dec 16, 2015 at 11:44 PM, Peter Geoghegan <p...@heroku.com> wrote: >> In any case, at this point 9.5 is really aimed to be stabilized, so >> targeting only master is a far saner approach IMO for this patch. >> Pushing that in 9.5 a couple of months back may have given enough >> reason to do so... But well life is life. > > No, this really isn't an optimization at all.
I should add: I think that the chances of this patch destabilizing the code are very slim, once it receives the proper review. Certainly, I foresee no possible downside to not inserting the doomed IndexTuple, since it's guaranteed to have its heap tuple super-deleted immediately afterwards. That's the only real behavioral change proposed here. So, I would prefer it if we got this in before the first stable release of 9.5. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
