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

From: Gábor Farkas <gabor(at)nekomancer(dot)net>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: vacuum, dead rows, usual solutions didn't help
Date: 2008-01-10 10:18:24
Message-ID: 4785F0F0.2060800@nekomancer.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Clodoaldo 2008-01-10 10:30:00 Re: Performance problem. Could it be related to 8.3-beta4?
Previous Message Simon Riggs 2008-01-10 09:51:34 Re: vacuum, dead rows, usual solutions didn't help