Of the times the execution of VACUUM asks for too time therefore I want
to interrupt.
Now to do it I shutdown the system.
It exists a better system ?

Is it possible AUTOVACUUM on
Version 7.4.19 ?

Thank's
--

Paolo Holzl <software (AT) toglispamtek-up (DOT) com> wrote:
How about:

SET statement_timeout=<maximum time in milliseconds>;
VACUUM atable;
SET statement_timeout=0;

That would interrupt the VACUUM if it takes too long, cancelling all its
effects.

There is an "autovacuum" contrib module in 7.4, according to
http://www.postgresql.org/docs/8.3/s...lease-7-4.html

I don't know how stable it is; autovacuum has definitely improved a
lot since it was included into PostgreSQL core.

Yours,
Laurenz Albe

Paolo Holzl <software (AT) toglispamtek-up (DOT) com> wrote:
How about:

SET statement_timeout=<maximum time in milliseconds>;
VACUUM atable;
SET statement_timeout=0;

That would interrupt the VACUUM if it takes too long, cancelling all its
effects.

There is an "autovacuum" contrib module in 7.4, according to
http://www.postgresql.org/docs/8.3/s...lease-7-4.html

I don't know how stable it is; autovacuum has definitely improved a
lot since it was included into PostgreSQL core.

Yours,
Laurenz Albe

Paolo Holzl <software (AT) toglispamtek-up (DOT) com> wrote:
How about:

SET statement_timeout=<maximum time in milliseconds>;
VACUUM atable;
SET statement_timeout=0;

That would interrupt the VACUUM if it takes too long, cancelling all its
effects.

There is an "autovacuum" contrib module in 7.4, according to
http://www.postgresql.org/docs/8.3/s...lease-7-4.html

I don't know how stable it is; autovacuum has definitely improved a
lot since it was included into PostgreSQL core.

Yours,
Laurenz Albe

Paolo Holzl <software (AT) toglispamtek-up (DOT) com> wrote:
How about:

SET statement_timeout=<maximum time in milliseconds>;
VACUUM atable;
SET statement_timeout=0;

That would interrupt the VACUUM if it takes too long, cancelling all its
effects.

There is an "autovacuum" contrib module in 7.4, according to
http://www.postgresql.org/docs/8.3/s...lease-7-4.html

I don't know how stable it is; autovacuum has definitely improved a
lot since it was included into PostgreSQL core.

Yours,
Laurenz Albe

Paolo Holzl <software (AT) toglispamtek-up (DOT) com> wrote:
How about:

SET statement_timeout=<maximum time in milliseconds>;
VACUUM atable;
SET statement_timeout=0;

That would interrupt the VACUUM if it takes too long, cancelling all its
effects.

There is an "autovacuum" contrib module in 7.4, according to
http://www.postgresql.org/docs/8.3/s...lease-7-4.html

I don't know how stable it is; autovacuum has definitely improved a
lot since it was included into PostgreSQL core.

Yours,
Laurenz Albe

Paolo Holzl <software (AT) toglispamtek-up (DOT) com> wrote:
How about:

SET statement_timeout=<maximum time in milliseconds>;
VACUUM atable;
SET statement_timeout=0;

That would interrupt the VACUUM if it takes too long, cancelling all its
effects.

There is an "autovacuum" contrib module in 7.4, according to
http://www.postgresql.org/docs/8.3/s...lease-7-4.html

I don't know how stable it is; autovacuum has definitely improved a
lot since it was included into PostgreSQL core.

Yours,
Laurenz Albe

Paolo Holzl <software (AT) toglispamtek-up (DOT) com> wrote:
How about:

SET statement_timeout=<maximum time in milliseconds>;
VACUUM atable;
SET statement_timeout=0;

That would interrupt the VACUUM if it takes too long, cancelling all its
effects.

There is an "autovacuum" contrib module in 7.4, according to
http://www.postgresql.org/docs/8.3/s...lease-7-4.html

I don't know how stable it is; autovacuum has definitely improved a
lot since it was included into PostgreSQL core.

Yours,
Laurenz Albe

Paolo Holzl <software (AT) toglispamtek-up (DOT) com> wrote:
How about:

SET statement_timeout=<maximum time in milliseconds>;
VACUUM atable;
SET statement_timeout=0;

That would interrupt the VACUUM if it takes too long, cancelling all its
effects.

There is an "autovacuum" contrib module in 7.4, according to
http://www.postgresql.org/docs/8.3/s...lease-7-4.html

I don't know how stable it is; autovacuum has definitely improved a
lot since it was included into PostgreSQL core.

Yours,
Laurenz Albe