Tom Lane wrote: > Alvaro Herrera <alvhe...@alvh.no-ip.org> writes: > >> 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. > > Where are we on this --- do you want me to push the brin_doupdate > fix I proposed, or were you intending to merge that into a > larger patch?
Please push your fixes, I'll post my proposed patch for the other bug afterwards; they are unrelated problems after all. If you prefer me to push your fixes, I can do that -- let me know. > If I'm to do it, is there a reason not to back-patch to all branches > with BRIN? No, all these fixes should go back to 9.5. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers