Re: A couple of regression test anomalies

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: A couple of regression test anomalies
Date: 2009-05-27 21:09:03
Message-ID: 200905280009.04644.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Monday 25 May 2009 00:55:17 Tom Lane wrote:
> 2. In tsearch.sql, there are multiple places where the test is trying
> to exercise some just-created index. This works as expected if the
> tests are run serially, but the indexes are (usually) not used if the
> tests are run in parallel. The reason is that the table was UPDATEd
> earlier in the test, so it has broken HOT chains, and other tests that
> are run concurrently with this one usually have open transactions that
> are older than the index.
>
> There are a number of possible responses to #2, for instance:
>
> 2A. We could opine that this is not a bug; the whole point of running
> parallel tests is to exercise code paths that are not taken in the
> serial tests.

It might be useful to add another test case that exercises the other code path
in parallel mode anyway, e.g., a similar table that is not updated earlier in
the test.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-05-27 21:14:32 Re: search_path vs extensions
Previous Message Tom Lane 2009-05-27 21:07:27 Re: [PATCH] plpythonu datatype conversion improvements