Re: BUG #15995: VACUUM not working after setting/unsetting of archive_mode = on, wal_level = replica

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jo(dot)raj(dot)postgres(dot)dba(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15995: VACUUM not working after setting/unsetting of archive_mode = on, wal_level = replica
Date: 2019-09-09 04:22:38
Message-ID: 2004.1568002958@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> 9. VACUUM is not working, even after upgrades vacuum is not working. If I
> unset archive_mode = on, wal_level = replica and leave to default, vacuum
> not working. Following is the message I get, no dead rows removed, but lot
> of delete/update has happeded to the table.

There are basically two possibilities here:

1. You have an old open transaction somewhere. Possibly an
uncommitted two-phase transaction. The pg_prepared_xacts view
would help identify the latter.

2. You have a replication slot that's holding back global xmin.
Look in pg_replication_slots.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2019-09-09 08:42:56 Re: BUG #15977: Inconsistent behavior in chained transactions
Previous Message fn ln 2019-09-09 03:58:46 Re: BUG #15977: Inconsistent behavior in chained transactions