From: Guillaume Lelarge <guillaume@lelarge.info>
To: Baptiste LHOSTE <blhoste@alaloop.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: [Autovacuum] Issue to understand some logs
Date: Mon, 17 Dec 2012 17:02:53 +0100
Message-ID: <1355760173.1977.14.camel@localhost.localdomain> (raw)
In-Reply-To: <157467040.1756135.1355759855861.JavaMail.root@alaloop.com>
References: <157467040.1756135.1355759855861.JavaMail.root@alaloop.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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.infohttp://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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: guillaume@lelarge.info, blhoste@alaloop.com
Subject: Re: [Autovacuum] Issue to understand some logs
In-Reply-To: <1355760173.1977.14.camel@localhost.localdomain>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox