Postgresql – Is it safe to kill vacuumdb

postgresqlvacuum

I would like to schedule a vacuumdb cron job for an entire database, but I don't want it to run past a certain time. Is it safe to just stop the job with killall vacuumdb?

Best Answer

Yes, it's safe. Use SIGTERM (the default, signal 15 on Linux) not SIGKILL (signal 9). If it doesn't complete it might waste recent work and have to repeat it.

However, you should really just let autovacuum do its job.

Related Solutions

Sql-server – Transfer data from database1 to database2 using task queue

You should be able to use triggers and dbilink to sync your data if you're prepared to install plperl on the postgresql end. If you are running version 9.1+ then you could instead try the foreign-data-wrapper functionality. There appear to be tds and fdw wrappers, though I've not used either myself.

Unless I'm missing something, an external queue manager sounds overkill.

Postgresql – create a batch script on windows that periodically starts a sql function

Use psql with a command to execute the function, eg:

postgres=> create function f() returns void language plpgsql as $$begin null; end;$$;
CREATE FUNCTION
postgres=> \q

root@maidenhead:~# psql --command="select f()" postgres postgres
 f
---

(1 row)

...which is easily set up to run via Task Scheduler, no batch file required (thanks @Craig)

Best Answer

Related Solutions

Sql-server – Transfer data from database1 to database2 using task queue

Postgresql – create a batch script on windows that periodically starts a sql function

Related Question