Re: Partial index creation always scans the entire table - Mailing list pgsql-performance

From Justin Pryzby
Subject Re: Partial index creation always scans the entire table
Date
Msg-id 20200217005226.GK31889@telsasoft.com
Whole thread Raw
In response to RE: Partial index creation always scans the entire table  ("Mike Sofen" <msofen@runbox.com>)
List pgsql-performance
On Sun, Feb 16, 2020 at 04:43:10PM -0800, Mike Sofen wrote:
> >From: Tom Lane <tgl@sss.pgh.pa.us>   Sent: Sunday, February 16, 2020 7:30
> AM
> >I've seen people try to do this before.  I wonder if the manual page about
> partial indexes should explicitly say "don't do that". 
> >    regards, tom lane
> 
> Yes please (seriously).  The utter beauty of Postgres is the flexibility and
> power that its evolutionary path has allowed/created.  The tragic danger is
> that the beauty is fairly easy to misapply/misuse.

Quote. Enough rope to shoot yourself in the foot.

Would you care to suggest text to be included here ?
https://www.postgresql.org/docs/devel/indexes-partial.html

-- 
Justin



pgsql-performance by date:

Previous
From: "Mike Sofen"
Date:
Subject: RE: Partial index creation always scans the entire table
Next
From: Tom Lane
Date:
Subject: Re: Partial index creation always scans the entire table