On Mon, Sep 5, 2016 at 8:57 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote: >> What performance difference does this make, in a realistic use case? > > I have yet to measure performance effect but it would be effect for > very large frozen table.
I think if you are proposing this patch because you think that the existing code won't perform well, you definitely need to submit some performance results showing that your approach is better. If you can't show that your approach is practically better (rather than just theoretically better), then I'm not sure we should change anything. It's very easy to screw up the code in this area and we do not want to risk corrupting data for the sake of an optimization that isn't really needed in the first place. Of course, if you can prove that the change has a significant benefit, then it's definitely worth considering. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
