Re: Minmax indexes

Поиск
Список
Период
Сортировка
От Jaime Casanova
Тема Re: Minmax indexes
Дата
Msg-id CAJKUy5hUVMz2ZxuzRN9M45nAJ6fX=nPu4pGz4oMNKn-O9W7j-w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Minmax indexes  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: Minmax indexes  (Jeff Janes <jeff.janes@gmail.com>)
Список pgsql-hackers
On Thu, Jul 10, 2014 at 3:50 PM, Josh Berkus <josh@agliodbs.com> wrote:
> 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.
>

How is this different from "ALTER TABLE foo SET (FILLFACTOR=80); " or
from "ALTER TABLE foo ALTER bar SET STORAGE EXTERNAL; " ?

we don't get a notice for these cases either

--
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566         Cell: +593 987171157



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Pg_upgrade and toast tables bug discovered
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Proposal for CSN based snapshots