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

On Jan 10, 2008, at 6:01 AM, Simon Riggs wrote:

> On Thu, 2008-01-10 at 11:18 +0100, Gábor Farkas wrote:
>> 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?
>
> They might be different set of dead rows, just roughly the same
> numbers
> each day.

Or, put another way, this is probably the same problem recurring, not
one constant instance of the issue.

Erik Jones

DBA | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)

Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com