Alvaro Herrera wrote: > Tomas Vondra wrote: > > > FWIW I can reproduce this on 9.5, and I don't even need to run the > > UPDATE part. That is, INSERT + VACUUM running concurrently is enough to > > produce broken BRIN indexes :-( > > Hmm, I'm pretty sure we stress-tested brin in pretty much the same way. > But I see this misbehavior too. Looking ...
Turns out that this is related to concurrent growth of the table while the summarization process is scanning -- so new pages have appeared at the end of the table after the end point has been determined. It would be a pain to determine number of blocks for each range, so I'm looking for a simple way to fix it without imposing so much overhead. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
