Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Yqm8E-0006u0-EP for pgsql-hackers@arkaria.postgresql.org; Fri, 08 May 2015 17:32:14 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Yqm8D-0008Mc-Sw for pgsql-hackers@arkaria.postgresql.org; Fri, 08 May 2015 17:32:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Yqm8C-0008KO-Bf for pgsql-hackers@postgresql.org; Fri, 08 May 2015 17:32:12 +0000 Received: from mail.anarazel.de ([217.115.131.40]) by magus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1Yqm85-0002CJ-NF for pgsql-hackers@postgresql.org; Fri, 08 May 2015 17:32:11 +0000 Received: from intern.anarazel.de (unknown [184.23.178.130]) (Authenticated sender: andres@anarazel.de) by mail.anarazel.de (Postfix) with ESMTPSA id DB591860001; Fri, 8 May 2015 19:32:04 +0200 (CEST) Date: Fri, 8 May 2015 19:32:02 +0200 From: Andres Freund To: Tom Lane Cc: Peter Geoghegan , hlinnaka , Jeff Janes , Stephen Frost , Dean Rasheed , Bruce Momjian , Pg Hackers Subject: Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 Message-ID: <20150508173202.GP12950@alap3.anarazel.de> References: <20150508150340.GJ12950@alap3.anarazel.de> <9096.1431102730@sss.pgh.pa.us> <20150508165246.GO12950@alap3.anarazel.de> <10633.1431105922@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10633.1431105922@sss.pgh.pa.us> X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 2015-05-08 13:25:22 -0400, Tom Lane wrote: > Andres Freund writes: > > On 2015-05-08 12:32:10 -0400, Tom Lane wrote: > >> Looks like there's a CLOBBER_CACHE_ALWAYS issue ... > >> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jaguarundi&dt=2015-05-08%2011%3A52%3A00 > > > Currently index inferrence ignores indexes that aren't yet valid > > according to checkxmin. I'm tempted to think that is a mistake. I think > > we should throw an error instead; possbily at execution rather than plan > > time. > > If that's what is happening, then throwing an error is not going to fix > the problem of the regression test results being unstable; it'll just be > a different error that might or might not get thrown depending on timing. Yep, that was more a comment about how the behaviour generally should be. If the failure is indeed caused by checkxmin (trying to reproduce right now), we can just remove the updates in that subsection of the tests. They're not relevant. Greetings, Andres Freund -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers