Re: Database size Vs performance degradation

Поиск
Список
Период
Сортировка
От Miernik
Тема Re: Database size Vs performance degradation
Дата
Msg-id 20080730215834.5323.0.NOFFLE@turbacz.local
обсуждение исходный текст
Ответ на Database size Vs performance degradation  ("Dave North" <DNorth@signiant.com>)
Ответы Re: Database size Vs performance degradation  (Mark Roberts <mailing_lists@pandapocket.com>)
Список pgsql-performance
Valentin Bogdanov <valiouk@yahoo.co.uk> wrote:
> I am guessing that you are using DELETE to remove the 75,000
> unimportant.  Change your batch job to CREATE a new table consisting
> only of the 5,000 important. You can use "CREATE TABLE table_name AS
> select_statement" command. Then drop the old table. After that you can
> use ALTER TABLE to change the name of the new table to that of the old
> one.

I have a similar, but different situation, where I TRUNCATE a table with
60k rows every hour, and refill it with new rows. Would it be better
(concerning bloat) to just DROP the table every hour, and recreate it,
then to TRUNCATE it? Or does TRUNCATE take care of the boat as good as a
DROP and CREATE?

I am running 8.3.3 in a 48 MB RAM Xen, so performance matters much.

--
Miernik
http://miernik.name/

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

Предыдущее
От: "Dennis Brakhane"
Дата:
Сообщение: Re: how does pg handle concurrent queries and same queries
Следующее
От: Miernik
Дата:
Сообщение: what is less resource-intensive, WHERE id IN or INNER JOIN?