pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: peterhumaj@gmail.com
Subject: Supplement of procedure suggested
Date: Wed, 17 Jan 2024 15:53:34 +0000
Message-ID: <170550681492.659.303448608084425401@wrigleys.postgresql.org> (raw)

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/16/routine-vacuuming.html
Description:

In 
https://www.postgresql.org/docs/current/routine-vacuuming.html

section "25.1.5. Preventing Transaction ID Wraparound Failures" there is a
5-step procedure to handle the "database is not accepting commands"
situation, see "Instead, follow these steps:"

Please, add a notice about temporary tables - they can also prevent
vacuuming! 
This is hinted in section "25.1.6. The Autovacuum Daemon", but only
indirectly:
"Temporary tables cannot be accessed by autovacuum. Therefore, appropriate
vacuum and analyze operations should be performed via session SQL
commands."


Just today on a production, I performed (in a single-user mode) vacuum, even
vacuum freeze, and after ending it, DB still didn't accept users.

The useful detection SELECT was 
SELECT oid, oid::regclass, relkind, relfrozenxid, age(relfrozenxid) FROM
pg_class WHERE relfrozenxid <> 0  ORDER BY age(relfrozenxid);

Then I realized these were the temporary tables and dropped all the
temporary schemas ... once in a single-user mode :(


Message-ID: <170550681492.659.303448608084425401@wrigleys.postgresql.org>
Permalink:  ../170550681492.659.303448608084425401@wrigleys.postgresql.org/
Also on:    postgresql.org/message-id/170550681492.659.303448608084425401@wrigleys.postgresql.org

 · 

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-docs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, peterhumaj@gmail.com
  Subject: Re: Supplement of procedure suggested
  In-Reply-To: <170550681492.659.303448608084425401@wrigleys.postgresql.org>

* 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