Skip site navigation (1) Skip section navigation (2)

Re: vacuuming and manu updates

From: "Kevin Crenshaw" <kcrenshaw(at)viscient(dot)com>
To: "'Daniel Staal'" <DStaal(at)usa(dot)net>, <pgsql-novice(at)postgresql(dot)org>
Subject: Re: vacuuming and manu updates
Date: 2005-10-27 09:43:10
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
One option for automating your vacuum process 'a la cron' is to write a
batch file and then run it via the task scheduler at the desired interval.
You can find the task scheduler under: Start -> All Programs -> Accessories
-> System Tools -> Scheduled Tasks




-----Original Message-----
From: pgsql-novice-owner(at)postgresql(dot)org
[mailto:pgsql-novice-owner(at)postgresql(dot)org] On Behalf Of Daniel Staal
Sent: Wednesday, October 26, 2005 9:00 PM
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] vacuuming and manu updates

--As of Wednesday, October 26, 2005 8:57 AM -0700, 
operationsengineer1(at)yahoo(dot)com is alleged to have said:

> is there a way to automate the vacuum process on
> windows (think cron on linux)?

--As for the rest, it is mine.

I'm sure there is, but I haven't had to touch a Windows computer in a 
couple of years...

Daniel T. Staal

This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

In response to

pgsql-novice by date

Next:From: Neil SaundersDate: 2005-10-27 13:01:48
Subject: Re: Database design advice
Previous:From: Michael FuhrDate: 2005-10-27 06:04:40
Subject: Re: Who is logged in?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group