Re: vacuum, dead rows, usual solutions didn't help

Поиск
Список
Период
Сортировка
От Gábor Farkas
Тема Re: vacuum, dead rows, usual solutions didn't help
Дата
Msg-id 4785F0F0.2060800@nekomancer.net
обсуждение исходный текст
Ответ на Re: vacuum, dead rows, usual solutions didn't help  (Simon Riggs <simon@2ndquadrant.com>)
Ответы Re: vacuum, dead rows, usual solutions didn't help  (Lars Heidieker <lars@heidieker.de>)
Re: vacuum, dead rows, usual solutions didn't help  (Simon Riggs <simon@2ndquadrant.com>)
Список pgsql-general
Simon Riggs wrote:
>
>> also, even if it is wrong, can an 'idle-in-transaction' connection that
>> was opened today block the vacuuming of rows that were deleted yesterday?
>
> Yes, if the rows were deleted after the connection started.
>

to avoid any potential misunderstandings, i will summarize the situation:

1. the vacuum-cronjob refuses to remove dead rows since 1.jan.2008.

2. i know that no postgres-process is older than 7.jan.2008. (from "ps
aux | grep postgres", and except the postgres-system-processes)

how can this happen?


gabor

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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: vacuum, dead rows, usual solutions didn't help
Следующее
От: Clodoaldo
Дата:
Сообщение: Re: Performance problem. Could it be related to 8.3-beta4?