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

From Simon Riggs
Subject Re: vacuum, dead rows, usual solutions didn't help
Date
Msg-id 1199966463.4266.702.camel@ebony.site
Whole thread Raw
In response to Re: vacuum, dead rows, usual solutions didn't help  (Gábor Farkas <gabor@nekomancer.net>)
Responses Re: vacuum, dead rows, usual solutions didn't help
List pgsql-general
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.

--
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com


pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Kernel kills postgres process - help need
Next
From: Sebastián Baioni
Date:
Subject: Re: Can't make backup