| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Vinícius Abrahão <vinnix(dot)bsd(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Shayon Mukherjee <shayonj(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Proposal to Enable/Disable Index using ALTER INDEX |
| Date: | 2024-10-15 23:16:48 |
| Message-ID: | CAApHDvrJbghFBC7TD=qkw0wh=qaEQPnmd0jAq0RhHghtjmWNzQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 12 Oct 2024 at 22:41, Vinícius Abrahão <vinnix(dot)bsd(at)gmail(dot)com> wrote:
> You are going to disable the index but not the update of it? Why? Does it imply that when you are going to re-enable it you are going to recreate it?
It might be worth you reading the discussion and proposed patches. I
think either of those would answer your questions.
I don't recall anyone ever proposing that re-enabling the index would
result in it having to be rebuilt. If that was a requirement, then I'd
say there does not seem much point in the feature. You might as well
just drop the index and recreate it if you change your mind.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2024-10-15 23:25:38 | Re: Proposal to Enable/Disable Index using ALTER INDEX |
| Previous Message | Masahiko Sawada | 2024-10-15 22:26:48 | Re: Fix for consume_xids advancing XIDs incorrectly |