| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Claudio Freire <klaussfreire(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Minmax indexes |
| Date: | 2014-07-10 20:50:05 |
| Message-ID: | 53BEFC7D.2070000@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/10/2014 12:20 PM, Alvaro Herrera wrote:
>> So I guess the only thing left is to issue a NOTICE when said alter
>> > takes place (I don't see that on the patch, but maybe it's there?)
> That's not in the patch. I don't think we have an appropriate place to
> emit such a notice.
What do you mean by "don't have an appropriate place"?
The suggestion is that when a user does:
ALTER INDEX foo_minmax SET PAGES_PER_RANGE=100
they should get a NOTICE:
"NOTICE: changes to pages per range will not take effect until the index
is REINDEXed"
otherwise, we're going to get a lot of "I Altered the pages per range,
but performance didn't change" emails.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-07-10 21:11:19 | Re: Pg_upgrade and toast tables bug discovered |
| Previous Message | Bruce Momjian | 2014-07-10 20:33:40 | Re: Pg_upgrade and toast tables bug discovered |