pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: pavan95 <pavan.postgresdba@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: 8.2 Autovacuum BUG ?
Date: Mon, 22 Jan 2018 03:21:39 -0700 (MST)
Message-ID: <1516616499481-0.post@n3.nabble.com> (raw)
In-Reply-To: <987851516614060@web46o.yandex.ru>
References: <46D83427.60001@livedatagroup.com>
	<1516601350338-0.post@n3.nabble.com>
	<987851516614060@web46o.yandex.ru>

Hello Sergi,

The size of the database is 24GB.

The output of the above query is :

 datid  | datname  | procpid | usesysid | usename  | application_name |
client_addr | client_hostname | client_port |          backend_start          
|            xact_start            |           query_start            |
waiting |            current_query             
--------+----------+---------+----------+----------+------------------+-------------+-----------------+-------------+----------------------------------+----------------------------------+----------------------------------+---------+--------------------------------------
 400091 | prod_erp |   19373 |       10 | postgres |                  |            
|                 |             | 2018-01-22 15:40:38.163865+05:30 |
2018-01-22 15:40:38.655754+05:30 | 2018-01-22 15:40:38.655754+05:30 | f      
| autovacuum: ANALYZE public.table1
 400091 | prod_erp |   19373 |       10 | postgres |                  |            
|                 |             | 2018-01-22 15:40:38.163865+05:30 |
2018-01-22 15:40:38.655754+05:30 | 2018-01-22 15:40:38.655754+05:30 | f      
| autovacuum: ANALYZE public.table1
400091 | prod_erp |   19373 |       10 | postgres |                  |            
|                 |             | 2018-01-22 15:40:38.163865+05:30 |
2018-01-22 15:40:38.218954+05:30 | 2018-01-22 15:40:38.218954+05:30 | f      
| autovacuum: ANALYZE public.table2
400091 | prod_erp |   18440 |       10 | postgres |                  |            
|                 |             | 2018-01-22 15:39:38.128879+05:30 |
2018-01-22 15:39:38.166507+05:30 | 2018-01-22 15:39:38.166507+05:30 | f      
| autovacuum: VACUUM public.table3


Could you please explain what antiwraparound autovacuum is?? Is it related
for preventing transactionID wraparound failures?  If so does running vacuum
full against the database will suppress this abnormal generation of archive
logs??

Please give your kind advice.

Regards,
Pavan




--
Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html




view thread (46+ messages)  latest in thread

Message-ID: <1516616499481-0.post@n3.nabble.com>
Permalink:  ../1516616499481-0.post@n3.nabble.com/
Also on:    postgresql.org/message-id/1516616499481-0.post@n3.nabble.com

 · 

reply
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-performance@postgresql.org
  Cc: pavan.postgresdba@gmail.com
  Subject: Re: 8.2 Autovacuum BUG ?
  In-Reply-To: <1516616499481-0.post@n3.nabble.com>

* 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