| From: | Victor Yegorov <vyegorov(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bill Moran <wmoran(at)potentialtech(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Disabling an index temporarily |
| Date: | 2015-12-14 07:30:35 |
| Message-ID: | CAGnEboiBsrGee12f+UkhMzRoAjC2qWKT-8z68Df4g-2gkj1aXg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2015-12-14 5:34 GMT+02:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Maybe I misunderstood, but I thought what was being discussed here is
> preventing the planner from selecting an index for use in queries, while
> still requiring all table updates to maintain validity of the index.
>
The O-ther big DBMS has `ALTER INDEX ... INVISIBLE` feature, that does
exactly this.
I was thinking of a function, similar to `set_config()`, for it has
`is_local` parameter, making it possible to adjust just current session or
a global behavior.
`set_index(name, is_visible, is_local` perhaps?
--
Victor Y. Yegorov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2015-12-14 07:36:49 | Re: Proposal: custom compression methods |
| Previous Message | Chapman Flack | 2015-12-14 07:27:58 | Re: Proposal: custom compression methods |