Redshift VACUUM cannot run inside a transaction block on SQLWorkbenchJ

vacuum sql-workbench-j
Ting Jia picture Ting Jia · Nov 30, 2015 · Viewed 14.2k times · Source

I have got a:

VACUUM cannot run inside a transaction block

error on SQLWorkbenchJ in Redshift, but I already commit all transactions before this.

Answer

a_horse_with_no_name picture a_horse_with_no_name · Nov 30, 2015

You don't need to change the connection profile, you can change the autocommit property inside your SQL script "on-the-fly" with set autocommit

set autocommit on;
vacuum;
set autocommit off;

You can also toggle the current autocommit state through the menu "SQL -> Autocommit"

Related questions

How to vacuum sqlite database?

I want to know how to vacuum sqlite database. I tried a syntax MANUAL VACUUM command for the whole database from command prompt: $sqlite3 database_name "VACUUM;"; But it's giving error as: near "database_name": syntax error. and also AUTO …

Read More
How do I know if the statistics of a Postgres table are up to date?

In pgAdmin, whenever a table's statistics are out-of-date, it prompts: Running VACUUM recommended The estimated rowcount on the table schema.table deviates significantly from the actual rowcount. You should run VACUUM ANALYZE on this table. I've tested it using pgAdmin 3 …

Read More
What does it mean to vacuum a database?

As referenced by this Firefox bug, what does the act of vacuuming a database accomplish? Is this operation supported by all modern database software, or only certain ones?

Read More