jesh Kumar Mallah"
To: "Tom Lane"
Cc: "John Lister" ;
Sent: Wednesday, February 11, 2009 3:37 PM
Subject: Re: [ADMIN] controlling autovacuum during the day.
On Wed, Dec 17, 2008 at 7:17 PM, Tom Lane wrote:
"John Lister" writes:
I'd like to use autova
On Wed, Dec 17, 2008 at 7:17 PM, Tom Lane wrote:
> "John Lister" writes:
>> I'd like to use autovacuum to clean up the tables rather than schedule a
>> full vacuum with cron as it will be more selective/intelligent about what
>> gets cleaned. But is it possible to stop it running during peak/offi
Brad Nicholson wrote:
> Does this mean that if you are using autovac on 8.1, you should not use
> the cost delay feature?
No, because the fix was also applied to 8.1.10.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
On Wed, 2008-12-17 at 13:31 -0300, Alvaro Herrera wrote:
> Michael Fuhr wrote:
> > On Wed, Dec 17, 2008 at 09:47:23AM -0500, Tom Lane wrote:
> > > "John Lister" writes:
> > > > Cheers for the quick reply. I've tweaked them quite a bit, but we have
> > > > quite
> > > > a few heavily updated tabl
Michael Fuhr wrote:
> On Wed, Dec 17, 2008 at 09:47:23AM -0500, Tom Lane wrote:
> > "John Lister" writes:
> > > Cheers for the quick reply. I've tweaked them quite a bit, but we have
> > > quite
> > > a few heavily updated tables that i'd like vacuuming to keep them in
> > > check.
> > > Unfor
On Wed, Dec 17, 2008 at 09:47:23AM -0500, Tom Lane wrote:
> "John Lister" writes:
> > Cheers for the quick reply. I've tweaked them quite a bit, but we have
> > quite
> > a few heavily updated tables that i'd like vacuuming to keep them in check.
> > Unfortunately the autovacuum does a FULL vac
John Lister wrote:
>> John Lister wrote:
>>
>>> bizarre... Its been turned off for a while, but from memory the
>>> autovacuum process was causing the table it was running on to be locked
>>> - I assumed this was an equivalent to VACUUM FULL - causing all other
>>> connections to wait until it had
John Lister wrote:
bizarre... Its been turned off for a while, but from memory the
autovacuum process was causing the table it was running on to be locked
- I assumed this was an equivalent to VACUUM FULL - causing all other
connections to wait until it had finished. Could this happen another wa
John Lister wrote:
> bizarre... Its been turned off for a while, but from memory the
> autovacuum process was causing the table it was running on to be locked
> - I assumed this was an equivalent to VACUUM FULL - causing all other
> connections to wait until it had finished. Could this happen
"John Lister" writes:
Cheers for the quick reply. I've tweaked them quite a bit, but we have
quite
a few heavily updated tables that i'd like vacuuming to keep them in
check.
Unfortunately the autovacuum does a FULL vacuum every so often locking
the
tables for quite a long time, i'd like to
"John Lister" writes:
> Cheers for the quick reply. I've tweaked them quite a bit, but we have quite
> a few heavily updated tables that i'd like vacuuming to keep them in check.
> Unfortunately the autovacuum does a FULL vacuum every so often locking the
> tables for quite a long time, i'd lik
"John Lister" writes:
I'd like to use autovacuum to clean up the tables rather than schedule a
full vacuum with cron as it will be more selective/intelligent about what
gets cleaned. But is it possible to stop it running during peak/office
hours?
No. Instead, set the vacuum cost parameters
"John Lister" writes:
> I'd like to use autovacuum to clean up the tables rather than schedule a
> full vacuum with cron as it will be more selective/intelligent about what
> gets cleaned. But is it possible to stop it running during peak/office
> hours?
No. Instead, set the vacuum cost param
I'd like to use autovacuum to clean up the tables rather than schedule a
full vacuum with cron as it will be more selective/intelligent about what
gets cleaned. But is it possible to stop it running during peak/office
hours?
I've seen a post mention using pg_autovacuum.enabled to do this, but
14 matches
Mail list logo
