Postgres Pro
Downloads
Home   >   mailing lists

Allow single table VACUUM in transaction block - Mailing list pgsql-hackers

From Simon Riggs
Subject Allow single table VACUUM in transaction block
Date
Msg-id CANbhV-EGkXfWymABGyNo0ZiwOW8=QZ84CmTrYSNSUq1-XbBC7g@mail.gmail.com
Whole thread Raw
Responses Re: Allow single table VACUUM in transaction block  (Simon Riggs <simon.riggs@enterprisedb.com>)
Re: Allow single table VACUUM in transaction block  (Justin Pryzby <pryzby@telsasoft.com>)
Re: Allow single table VACUUM in transaction block  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
Tree view 
It is a common user annoyance to have a script fail because someone
added a VACUUM, especially when using --single-transaction option.
Fix, so that this works without issue:

BEGIN;
....
VACUUM (ANALYZE) vactst;
....
COMMIT;

Allows both ANALYZE and vacuum of toast tables, but not VACUUM FULL.

When in a xact block, we do not set PROC_IN_VACUUM,
nor update datfrozenxid.

Tests, docs.

--
Simon Riggs                http://www.EnterpriseDB.com/
Attachment

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures
Next
From: Richard Guo
Date:
Subject: Avoid using list_delete_first in simplify_or/and_arguments