Optimization of partial index creation for a new column - Mailing list pgsql-hackers

From Александр Асафов
Subject Optimization of partial index creation for a new column
Date
Msg-id CAFscNDDjy-HsfiZuQi8MhPof5200P8u-Ye4=jhvWp6YLmvYs1w@mail.gmail.com
Whole thread Raw
Responses Re: Optimization of partial index creation for a new column
List pgsql-hackers
Hello hackers,
I have a feature suggestion to optimize the creation of a partial
index. In some cases, it is possible to skip a full table scan. For
example:

BEGIN;
ALTER TABLE test ADD COLUMN (newcol int);
CREATE INDEX newindex ON test(newcol) WHERE newcol IS NOT NULL;
COMMIT;

In this case, the values of all columns in the new table will be NULL,
and there is no point in checking the conditions for each row. The
same optimization can be done for default values in NOT NULL columns.

How complex would a patch with this optimization be? Will it be
necessary to add any attributes to the table metadata, or can we check
that the previous command was CREATE TABLE when creating an index?



pgsql-hackers by date:

Previous
From: Corey Huinker
Date:
Subject: Re: Import Statistics in postgres_fdw before resorting to sampling.
Next
From: Sadeq Dousti
Date:
Subject: Re: psql \dh: List High-Level (Root) Tables and Indexes