Simon Riggs wrote: > The first "half" is actually quite large, but that makes it even more > sensible to commit this part now. > > The enclosed patch introduces the machinery by which we might later > optimise hint bit setting. It differentiates between hint bit setting > and block dirtying, when the distinction can safely be made. It acts > safely during VACUUM and correctly during checkpoint. In all other > respects it emulates current behaviour.
I think it makes sense to commit this patch now, per previous discussions on which we have agreed to make incremental changes. I think we should just get rid of the bogus changes Pavan identified. I'm just wondering if the change of usage_count from 16 to 8 bits was discussed and agreed? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-patches mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches