From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Baptiste LHOSTE <blhoste(at)alaloop(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: [Autovacuum] Issue to understand some logs |
Date: | 2012-12-17 16:02:53 |
Message-ID: | 1355760173.1977.14.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Baptiste LHOSTE | 2012-12-17 16:10:18 | Re: [Autovacuum] Issue to understand some logs |
Previous Message | Baptiste LHOSTE | 2012-12-17 15:57:35 | [Autovacuum] Issue to understand some logs |