| From: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Paul Martinez <hellopfm(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PROPOSAL: Support global and local disabling of indexes |
| Date: | 2022-03-18 13:01:59 |
| Message-ID: | CAMjNa7cNNq_so_OE51Y-r07VSOmBD3cRZvteFvBRH0DGn8kMMA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Just wanted to mention that this would be a useful feature for me. Had
previously been bitten by this:
https://www.postgresql.org/message-id/flat/CAMjNa7c4pKLZe%2BZ0V49isKycnXQ6Y%3D3BO-4Gsj3QAwsd2r7Wrw%40mail.gmail.com
Ended up "solving" by putting a where clause on all my exclusion
constraints I didn't want used for most queries (WHERE 1=1). That allowed
me "disable" that index for all queries unless they explicitly have a 1=1
constant in the where clause.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2022-03-18 13:50:01 | Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15) |
| Previous Message | Nitin Jadhav | 2022-03-18 11:22:52 | Re: Report checkpoint progress with pg_stat_progress_checkpoint (was: Report checkpoint progress in server logs) |