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? If I'm to do it, is there a reason not to back-patch to all branches with BRIN? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers