On Thu, Mar 22, 2012 at 9:31 AM, Simon Riggs <si...@2ndquadrant.com> wrote: > Surely it just stops you using that idea 100% of the time. I don't see > why you can't have this co-exist with the current mechanism. So it > doesn't kill it for the common case.
I guess you could use it if you knew that there were no DELETE or UPDATE statements in progress on that table, but it seems like figuring that out would be more trouble than it's worth. > But would the idea deliver much value? Is line pointer bloat a > problem? (I have no idea if it is/is not) Good question. I think that all things being equal it would be worth getting rid of, but I'm not sure it's worth paying a lot for. Maybe when I have time I'll try to gather some statistics. -- 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
