On 2016-07-01 15:42:22 -0500, Jim Nasby wrote: > On 7/1/16 2:23 PM, Andres Freund wrote: > > > > The only > > > > cost of that is that vacuum will come along and mark the page > > > > all-visible again instead of skipping it, but that's probably not an > > > > enormous expense in most cases. > > I think the main cost is not having the page marked as all-visible for > > index-only purposes. If it's an insert mostly table, it can be a long > > while till vacuum comes around. > > ISTM that's something that should be addressed anyway (and separately), no?
Huh? That's the current behaviour in heap_lock_tuple. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
