Re: Guidelines on dropping objects in regression tests, sqlsmith

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, seltenreich(at)gmx(dot)de
Subject: Re: Guidelines on dropping objects in regression tests, sqlsmith
Date: 2018-04-15 03:02:09
Message-ID: 1327.1523761329@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> I took a look through all of the SQL files that the INCLUDE covering
> indexes patch added tests to. At no point do they leave behind any
> INCLUDE indexes. I'll do something about that as part of the INCLUDE
> patch that I'm working on at the moment.

A quick look at the current final state of the regression database
says

regression=# select indexrelid::regclass, indrelid::regclass from pg_index where indnatts != indnkeyatts;
indexrelid | indrelid
---------------------+-------------
covidxpart1_a_b_idx | covidxpart1
covidxpart_a_b_idx | covidxpart
covidxpart2_a_b_idx | covidxpart2
covidxpart3_a_b_idx | covidxpart3
covidxpart4_a_b_idx | covidxpart4
(5 rows)

So we've got *some*, but it sure looks like they were all added by the
patch to fix covering indexes for partitions. I'd want to see some for
plain-table cases as well.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2018-04-15 03:28:07 Re: Guidelines on dropping objects in regression tests, sqlsmith
Previous Message Amit Langote 2018-04-15 02:58:03 Re: partitioning code reorganization