Re: vacuum, dead rows, usual solutions didn't help - Mailing list pgsql-general

From Gábor Farkas
Subject Re: vacuum, dead rows, usual solutions didn't help
Date
Msg-id 4785F0F0.2060800@nekomancer.net
Whole thread Raw
In response to Re: vacuum, dead rows, usual solutions didn't help  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: vacuum, dead rows, usual solutions didn't help
Re: vacuum, dead rows, usual solutions didn't help
List 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 by date:

Previous
From: Simon Riggs
Date:
Subject: Re: vacuum, dead rows, usual solutions didn't help
Next
From: Clodoaldo
Date:
Subject: Re: Performance problem. Could it be related to 8.3-beta4?