Re: Guidelines on dropping objects in regression tests, sqlsmith - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Guidelines on dropping objects in regression tests, sqlsmith
Date
Msg-id 1327.1523761329@sss.pgh.pa.us
Whole thread Raw
In response to Re: Guidelines on dropping objects in regression tests, sqlsmith  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Guidelines on dropping objects in regression tests, sqlsmith  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
Peter Geoghegan <pg@bowt.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


pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: partitioning code reorganization
Next
From: Peter Geoghegan
Date:
Subject: Re: Guidelines on dropping objects in regression tests, sqlsmith