On Wed, Oct 21, 2015 at 1:31 PM, Jeff Janes <jeff.ja...@gmail.com> wrote: > It turns out it was pretty easy to set PD_ALL_VISIBLE on the new pages, > since the code in hio that requests the relation to be extended already has > info on the tuple's intended freeze status. > > Then you just need to refrain from clearing PD_ALL_VISIBLE when that tuple > is actually written into the page. Not only because clearing would defeat > the purpose, but also because it will cause an error--apparently the > incipient page is not yet in a state where visibilitymap_clear is willing to > deal with it.
Wouldn't it be better to instead fill the page with tuples first and THEN set PD_ALL_VISIBLE? -- 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
