Date: Sun, 16 Feb 2020 18:52:26 -0600
From: Justin Pryzby <pryzby@telsasoft.com>
To: Mike Sofen <msofen@runbox.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Laurenz Albe <laurenz.albe@cybertec.at>,
	MingJu Wu <mingjuwu0505@gmail.com>,
	pgsql-performance@lists.postgresql.org
Subject: Re: Partial index creation always scans the entire table
Message-ID: <20200217005226.GK31889@telsasoft.com>
References: 
 <CAKVFrvFY-f7kgwMRMiPLbPYMmgjc8Y2jjUGK_Y0HVcYAmU6ymg@mail.gmail.com>
 <43b329d274c3535c75d2fbd6912b5ae8e3e51582.camel@cybertec.at>
 <19549.1581867005@sss.pgh.pa.us>
 <05fc01d5e52b$3c3d1c50$b4b754f0$@runbox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <05fc01d5e52b$3c3d1c50$b4b754f0$@runbox.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Precedence: bulk

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