public inbox for [email protected]help / color / mirror / Atom feed
vacuumdb produces ERROR: cannot freeze committed xmax 6+ messages / 4 participants [nested] [flat]
* vacuumdb produces ERROR: cannot freeze committed xmax @ 2025-11-12 19:10 Sbob <[email protected]> 0 siblings, 3 replies; 6+ messages in thread From: Sbob @ 2025-11-12 19:10 UTC (permalink / raw) To: [email protected] All; running a vacuumdb is throwing this error on a PostgreSQL v15 db: vacuumdb: error: processing of database "prod1" failed: ERROR: cannot freeze committed xmax 1406773176 Thanks in advance for any guidance ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: vacuumdb produces ERROR: cannot freeze committed xmax @ 2025-11-12 20:19 Ron Johnson <[email protected]> parent: Sbob <[email protected]> 2 siblings, 0 replies; 6+ messages in thread From: Ron Johnson @ 2025-11-12 20:19 UTC (permalink / raw) To: Pgsql-admin <[email protected]> On Wed, Nov 12, 2025 at 2:10 PM Sbob <[email protected]> wrote: > > All; > > running a vacuumdb is throwing this error on a PostgreSQL v15 db: > Which *exact* version? > vacuumdb: error: processing of database "prod1" failed: ERROR: cannot > freeze committed xmax 1406773176 > What is the *exact* command? Any other errors (like in the PG log file)? -- Death to <Redacted>, and butter sauce. Don't boil me, I'm still alive. <Redacted> lobster! ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: vacuumdb produces ERROR: cannot freeze committed xmax @ 2025-11-13 08:59 Laurenz Albe <[email protected]> parent: Sbob <[email protected]> 2 siblings, 1 reply; 6+ messages in thread From: Laurenz Albe @ 2025-11-13 08:59 UTC (permalink / raw) To: Sbob <[email protected]>; [email protected] On Wed, 2025-11-12 at 12:10 -0700, Sbob wrote: > running a vacuumdb is throwing this error on a PostgreSQL v15 db: > > > vacuumdb: error: processing of database "prod1" failed: ERROR: cannot > freeze committed xmax 1406773176 That is data corruption: VACUUM encountered a tuple with a HEAP_XMAX_INVALID hint (which indicates the tuple is visible), but the deleting transaction is committed. Perhaps your commit log got corrupted. Is that on the same system as you other report that indicates a corrupted database? (https://postgr.es/m/0a1745be-c54d-43b9-a90f-71e4c721c17c%40quadratum-braccas.com) Perhaps it is time to restore a good backup. Yours, Laurenz Albe ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: vacuumdb produces ERROR: cannot freeze committed xmax @ 2025-11-13 11:06 Fabrice Chapuis <[email protected]> parent: Sbob <[email protected]> 2 siblings, 0 replies; 6+ messages in thread From: Fabrice Chapuis @ 2025-11-13 11:06 UTC (permalink / raw) To: Sbob <[email protected]>; +Cc: [email protected] Hi, This thread could perhaps help PostgreSQL: ERROR: cannot freeze committed xmax <https://www.postgresql.org/message-id/flat/8C414E45-6DD8-48E0-84B2-2D53545000D0%40gmail.com; Regards, Fabrice On Wed, Nov 12, 2025 at 8:10 PM Sbob <[email protected]> wrote: > > All; > > running a vacuumdb is throwing this error on a PostgreSQL v15 db: > > > vacuumdb: error: processing of database "prod1" failed: ERROR: cannot > freeze committed xmax 1406773176 > > > Thanks in advance for any guidance > > > > ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: vacuumdb produces ERROR: cannot freeze committed xmax @ 2025-11-13 17:16 Sbob <[email protected]> parent: Laurenz Albe <[email protected]> 0 siblings, 1 reply; 6+ messages in thread From: Sbob @ 2025-11-13 17:16 UTC (permalink / raw) To: Laurenz Albe <[email protected]>; [email protected] On 11/13/25 1:59 AM, Laurenz Albe wrote: > On Wed, 2025-11-12 at 12:10 -0700, Sbob wrote: >> running a vacuumdb is throwing this error on a PostgreSQL v15 db: >> >> >> vacuumdb: error: processing of database "prod1" failed: ERROR: cannot >> freeze committed xmax 1406773176 > That is data corruption: VACUUM encountered a tuple with a HEAP_XMAX_INVALID > hint (which indicates the tuple is visible), but the deleting transaction > is committed. > > Perhaps your commit log got corrupted. > > Is that on the same system as you other report that indicates a corrupted database? > (https://postgr.es/m/0a1745be-c54d-43b9-a90f-71e4c721c17c%40quadratum-braccas.com) Yes, we did a restore of the tables that seemed to be corrupted, any advice on determining the cause of the corruption? > > Perhaps it is time to restore a good backup. > > Yours, > Laurenz Albe ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: vacuumdb produces ERROR: cannot freeze committed xmax @ 2025-11-13 18:29 Laurenz Albe <[email protected]> parent: Sbob <[email protected]> 0 siblings, 0 replies; 6+ messages in thread From: Laurenz Albe @ 2025-11-13 18:29 UTC (permalink / raw) To: Sbob <[email protected]>; [email protected] On Thu, 2025-11-13 at 10:16 -0700, Sbob wrote: > Yes, we did a restore of the tables that seemed to be corrupted, any > advice on determining the cause of the corruption? Investigate what odd things you did with the database. In my experience, the main causes for corruption are: - shoddy or old hardware - bad administration (e.g., badly taken backups) - software bugs Yours, Laurenz Albe ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2025-11-13 18:29 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-11-12 19:10 vacuumdb produces ERROR: cannot freeze committed xmax Sbob <[email protected]> 2025-11-12 20:19 ` Ron Johnson <[email protected]> 2025-11-13 08:59 ` Laurenz Albe <[email protected]> 2025-11-13 17:16 ` Sbob <[email protected]> 2025-11-13 18:29 ` Laurenz Albe <[email protected]> 2025-11-13 11:06 ` Fabrice Chapuis <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox