| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Mike Sofen <msofen(at)runbox(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, MingJu Wu <mingjuwu0505(at)gmail(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Partial index creation always scans the entire table |
| Date: | 2020-02-17 00:52:26 |
| Message-ID: | 20200217005226.GK31889@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sun, Feb 16, 2020 at 04:43:10PM -0800, Mike Sofen wrote:
> >From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-02-17 01:09:00 | Re: Partial index creation always scans the entire table |
| Previous Message | Mike Sofen | 2020-02-17 00:43:10 | RE: Partial index creation always scans the entire table |