Request a Demo
Home   >   mailing lists

Re: Report oldest xmin source when autovacuum cannot remove tuples - Mailing list pgsql-hackers

From wenhui qiu
Subject Re: Report oldest xmin source when autovacuum cannot remove tuples
Date
Msg-id CAGjGUALq4QhHJsftYoqY=mi_1FgOZhhSg1pfoFvyP=9MWx4L_g@mail.gmail.com
Whole thread
In response to Re: Report oldest xmin source when autovacuum cannot remove tuples  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
Tree view
Hi 


> +static const char *const OldestXminBlockerNames[] = {
> + [OLDEST_XMIN_BLOCKER_NONE] = "none",
> + [OLDEST_XMIN_BLOCKER_RUNNING_XACT] = "running transaction",
> + [OLDEST_XMIN_BLOCKER_PREPARED_XACT] = "prepared transaction",
> + [OLDEST_XMIN_BLOCKER_STANDBY_FEEDBACK] = "standby feedback",
> + [OLDEST_XMIN_BLOCKER_REPLICATION_SLOT] = "replication slot",
> + [OLDEST_XMIN_BLOCKER_LOGICAL_SLOT] = "logical replication slot",
 
 No distinction was made between idle transactions and long-running transactions.It is very important to distinguish between them, as this is extremely helpful in guiding DBAs to identify the source of a OldestXminBlocker.
Thanks  

pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Fix races conditions in DropRole() and GrantRole()
Next
From: Shinya Kato
Date:
Subject: doc: REPACK is missing from the MAINTAIN privilege documentation