Message-ID: <1355760173.1977.14.camel@localhost.localdomain>
Subject: Re: [Autovacuum] Issue to understand some logs
From: Guillaume Lelarge <guillaume@lelarge.info>
To: Baptiste LHOSTE <blhoste@alaloop.com>
Cc: pgsql-admin@postgresql.org
Date: Mon, 17 Dec 2012 17:02:53 +0100
In-Reply-To: <157467040.1756135.1355759855861.JavaMail.root@alaloop.com>
References: <157467040.1756135.1355759855861.JavaMail.root@alaloop.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On Mon, 2012-12-17 at 16:57 +0100, Baptiste LHOSTE wrote:
> Hi everybody,
> 
> I have trouble understanding some logs of postgreSQL.
> 
> Here you can find a log from the auto-vacuum process :
> 
> 2012-12-17 16:38:58 CET LOG:  automatic vacuum of table "flows.public.agg_t344_outgoing_a41_src_net_and_dst_net_f5": index scans: 0
> 	pages: 0 removed, 59820 remain
> 	tuples: 0 removed, 5801752 remain
> 	system usage: CPU 0.93s/0.95u sec elapsed 423.07 sec
> 
> I am right to conclude that there is 5801752 available tuples in the previous table ?
> 
> If true, I am very confused because our table can not exceed 2592000 tuples (We delete old ones).
> 
> To be sure I tried to run the following query to count availables tuples :
> 
> select count(*) from agg_t344_outgoing_a41_src_net_and_dst_net_f5;
>   count  
> ---------
>  2584398
> (1 row)
> 
> Can someone give me a clue ?
> 

It could be dead rows, still visible for other transactions.


-- 
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin