On Tue, Feb 28, 2017 at 5:42 AM, Pavan Deolasee <pavan.deola...@gmail.com> wrote: > During the second heap scan of CREATE INDEX CONCURRENTLY, we're only > interested in the tuples which were inserted after the first scan was > started. All such tuples can only exists in pages which have their VM bit > unset. So I propose the attached patch which consults VM during second scan > and skip all-visible pages. We do the same trick of skipping pages only if > certain threshold of pages can be skipped to ensure OS's read-ahead is not > disturbed.
BTW, is there any danger of VACUUM acquiring a lock on the heap relation (i.e. vacuuming it) after the first CIC transaction ends, but before the second CIC transaction begins? -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
