Re: debugging handle exhaustion and 15 min/ 5mil row delete

Поиск
Список
Период
Сортировка
От Mark Stosberg
Тема Re: debugging handle exhaustion and 15 min/ 5mil row delete
Дата
Msg-id 20100507101031.3442dd08@summersault.com
обсуждение исходный текст
Ответ на Re: debugging handle exhaustion and 15 min/ 5mil row delete  (Marcos Ortiz <mlortiz@uci.cu>)
Ответы Re: debugging handle exhaustion and 15 min/ 5mil row delete  (Marcos Ortiz <mlortiz@uci.cu>)
Список pgsql-performance
> You can use TRUNCATE instead DELETE. TRUNCATE is more efficient and
> faster that DELETE.

Thanks for the suggestion. However, TRUNCATE is not compatible with
Slony, and we also have some rows which remain in table.

> Now, we need more information about your system to give you a certain
> solution:
> Are you using a RAID controller for you data?

Yes.

> Do you have separated the xlog directory from the data directory?

No.

> Which is your Operating System?

FreeBSD.

> Which is you architecture?

i386.

Thanks for the feedback. I'm going to try batching the deletes for now,
which is approach was worked well for some of our other long-running
deletes.

    Mark

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

Предыдущее
От: Marcos Ortiz
Дата:
Сообщение: Re: debugging handle exhaustion and 15 min/ 5mil row delete
Следующее
От: Alexander Korotkov
Дата:
Сообщение: Re: Planner issue on sorting joining of two tables with limit