If autovacuum is to be provided with facilities for individual table and time window controls, that can be done currently using VACUUM TABLE FULL. Currently this must be scheduled in crontab - a task scheduler in PGAdmin would be very helpful to do this instead of crontab that usually requires sysa
I guess I was thinking that if you do a vacuum analyze verbose from
within psql, it does vacuum the big 'insert only' tables. Of course
it never finds any dead rows, but it does take a long time to get
past those tables. I didn't know that autovacuum would be any different.
Behalf Of Joshua D. Drake
Sent: Wednesday, 12 April, 2006 12:51 am
To: Chris Hoover
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Autovacuum ideas
> This is one thing that is preventing me from turning on autovacuun,.
> However, due to the activity on them, they really need to be vacuu
Brendan Duddridge wrote:
What I'd like to see is a table exclusion list. I have a few very
large history tables that are never updated or deleted, only inserts
and selects.
Such a table will never trigger the vacuum rules as I understand them
(vacuum only happens on table that have obsolete t
On 13.04.2006, at 7:56 Uhr, Brendan Duddridge wrote:
What I'd like to see is a table exclusion list. I have a few very
large history tables that are never updated or deleted, only
inserts and selects.
But if you do selects regularly you may want to have the analyse part
of autovacuum for
What I'd like to see is a table exclusion list. I have a few very large history tables that are never updated or deleted, only inserts and selects. Brendan Duddridge | CTO | 403-277-5591 x24 | [EMAIL PROTECTED] ClickSpace Interac
I love this idea. I think on initial consideration it might have a lot of merit. You could have a setup something like:pg_av_grp -- table of group namesavgrpname varchar(50) -- group namepg_av_grp_window -- time windows when not to vacuum the group of tables
avgrpwinrelid = pg_av_group.oidno_run_
On Wednesday 12 April 2006 07:53, Chris Hoover wrote:
> This is what we are doing today (except we are on Linux :) ). However,
> since there is talk of making autovacuum on by default and the advantages
> of having it run, it would be nice to be able to block out hours that it
> can not run. It w
Chris Hoover wrote:
> This is what we are doing today (except we are on Linux :) ). However,
> since there is talk of making autovacuum on by default and the advantages of
> having it run, it would be nice to be able to block out hours that it can
> not run. It would also be very nice to have the
This is what we are doing today (except we are on Linux :) ). However, since there is talk of making autovacuum on by default and the advantages of having it run, it would be nice to be able to block out hours that it can not run. It would also be very nice to have the database take care of all o
Chris Hoover wrote:
> As far as I can tell, there is no way to tell the daemon to only do it's
> work between certain hours. Could this be added as an option? In my
> situation, I have tables that if vacuumed during the day would cause a
> noticeable slowdown to my users and has therefore been d
> This is one thing that is preventing me from turning on autovacuun,.
> However, due to the activity on them, they really need to be vacuumed
> daily. It would be nice to be able to tell autovacuum to run, but
> have a way to tell it to always sleep during these hours ( i.e. 7am to
> 5pm daily)
Hi Chris Hoover,
There is already a method for this! Can i suggest that you set a O/S
schedule to simple run vacuumdb.exe at the desired time, preferable late
evening, as the vacuum of large databases can take all night, based on
my DBA experience. Don’t for get to setup the uses of password
I have an idea/request for the autovacuum daemon.As far as I can tell, there is no way to tell the daemon to only do it's work between certain hours. Could this be added as an option? In my situation, I have tables that if vacuumed during the day would cause a noticeable slowdown to my users and
14 matches
Mail list logo
