From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Peter Geoghegan <pg@heroku.com>, hlinnaka <hlinnaka@iki.fi>,
 Jeff Janes <jeff.janes@gmail.com>, Stephen Frost <sfrost@snowman.net>,
 Dean Rasheed <dean.a.rasheed@gmail.com>, Bruce Momjian <bruce@momjian.us>,
 Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
In-reply-to: <20150508165246.GO12950@alap3.anarazel.de>
References: 
 <CAM3SWZTGE0z5_E8wRi9wt3qgOiMpSwtwr5uDcZDGhRZ1_pz6vg@mail.gmail.com>
 <20150508150340.GJ12950@alap3.anarazel.de> <9096.1431102730@sss.pgh.pa.us>
 <20150508165246.GO12950@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
 message dated "Fri, 08 May 2015 18:52:46 +0200"
Date: Fri, 08 May 2015 13:25:22 -0400
Message-ID: <10633.1431105922@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Andres Freund <andres@anarazel.de> 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.

			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