| From: | "Mike Sofen" <msofen(at)runbox(dot)com> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Laurenz Albe'" <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | "'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:43:10 |
| Message-ID: | 05fc01d5e52b$3c3d1c50$b4b754f0$@runbox.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>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. Caveats in the
documentation would be very beneficial to both seasoned practitioners and
newcomers - it is quite challenging to keep up with everything Postgres and
the documentation is where most of us turn for guidance.
And thank you Tom (and others), for your willingness to share these (and
many, many other) insights - it is so powerful when facts connect with
database reality.
Mike Sofen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2020-02-17 00:52:26 | Re: Partial index creation always scans the entire table |
| Previous Message | Lars Aksel Opsahl | 2020-02-16 17:15:25 | SubtransControlLock and performance problems |