Re: 7 hrs for a pg_restore?

Поиск
Список
Период
Сортировка
От Jeff Davis
Тема Re: 7 hrs for a pg_restore?
Дата
Msg-id 1203450679.3846.107.camel@dogma.ljc.laika.com
обсуждение исходный текст
Ответ на Re: 7 hrs for a pg_restore?  (Dave Cramer <pg@fastcrypt.com>)
Список pgsql-performance
On Tue, 2008-02-19 at 14:28 -0500, Dave Cramer wrote:
> shared buffers is *way* too small as is effective cache
> set them to 2G/6G respectively.

They are way too small, but I don't think that explains the index
creation time.

Effective_cache_size is only used by the planner, and this problem is
not caused by a poorly chosen plan.

It's important to set shared_buffers higher as well, but he has so much
RAM compared with his dataset that he's certainly not going to disk. I
don't think this explains it either.

I think it's just the result of building a lot of indexes on localized
text using only one core at a time.

Regards,
    Jeff Davis


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

Предыдущее
От: Jeff Davis
Дата:
Сообщение: Re: 7 hrs for a pg_restore?
Следующее
От: Jeff
Дата:
Сообщение: Re: 7 hrs for a pg_restore?