Hi Alvaro,
On Wed, Oct 29, 2008 at 3:46 PM, Alvaro Herrera
<[EMAIL PROTECTED]>wrote:
> Noah Freire escribió:
>
> > please check the first log message: the vacuum threshold is 6,000,050
> rows
> > and the number of dead tuples is 16,697,969. Even though the number of
> > dead_tuples is greater than
Noah Freire escribió:
> datid | datname | procpid | usesysid | usename | current_query | waiting |
> xact_start | query_start | backend_start | client_addr | client_port
> ---+-+-+--+--+-+-
Noah Freire escribió:
> please check the first log message: the vacuum threshold is 6,000,050 rows
> and the number of dead tuples is 16,697,969. Even though the number of
> dead_tuples is greater than the threshold the autovacuum is not being
> triggered for this table. So, besides this condition
Hello,
I have a table (accounts) with 600,000,000 rows. A heavy high-concurrent
workload that makes mostly updates on this table generates a lot of dead
tuples in its run, which is expected due to MVCC.
The problem is that even though autovacuum is enabled, the autovacuum worker
does not vacuum th
