From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Peter Geoghegan <pg(at)heroku(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
Date: | 2015-05-08 21:13:39 |
Message-ID: | 20150508211339.GY12950@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
On 2015-05-08 22:29:47 +0200, Andres Freund wrote:
> On 2015-05-08 15:22:09 -0400, Tom Lane wrote:
> > I'm back to suspecting that the indcheckxmin issue is the true cause of
> > the buildfarm failure
> > though we lack an explanation why Andres failed to reproduce it ...
>
> My laptop is probably a good bit faster than jaguarundi, particularly in
> a single "threaded" workload, as that test, due to turbo
> boost. Friarbird didn't trigger it either so far. It's quite possible
> that it requires a concurrent analyze or so to run to occur in the wrong
> moment.
prairiedog, without CCA, failed as well
http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=prairiedog&dt=2015-05-08%2019%3A55%3A11
different test, but again directly after index creation. So I hope it's
indeed the indcheckxmin thing.
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-05-08 21:51:27 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
Previous Message | Andres Freund | 2015-05-08 20:29:47 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-05-08 21:39:41 | Re: multixacts woes |
Previous Message | Robbie Harwood | 2015-05-08 20:39:15 | Postgres GSSAPI Encryption |