From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: brin regression test intermittent failures |
Date: | 2015-05-15 23:07:00 |
Message-ID: | 20150515230700.GM2523@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > Andrew Dunstan wrote:
> >> There's something odd about the brin regression tests. They seem to generate
> >> intermittent failures, which suggests some sort of race condition or
> >> ordering failure.
> >>
> >> See for example <http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=fulmar&dt=2015-05-15%2001%3A02%3A28>
> >> and <http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=sittella&dt=2015-05-15%2021%3A08%3A38>
>
> > Yeah it's pretty odd.
>
> Oooh. I saw the sittella failure and assumed it was triggered by the
> latest BRIN additions, but that fulmar failure is from before those hit.
>
> Just from reading the documentation, couldn't the symptom we're seeing
> arise from autovacuum having hit the table right before
> brin_summarize_new_values got called?
Well, I added a autovacuum_enabled=off to that table recently precisely
because that was my hypothesis. It didn't work though, so it must be
sometihng else.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-05-15 23:51:40 | Re: brin regression test intermittent failures |
Previous Message | Tom Lane | 2015-05-15 22:49:34 | Re: brin regression test intermittent failures |