pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedVacuum v/s Autovacuum
5+ messages / 4 participants
[nested] [flat]
* Vacuum v/s Autovacuum
@ 2007-01-18 13:24 Gauri Kanekar <meetgaurikanekar@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Gauri Kanekar @ 2007-01-18 13:24 UTC (permalink / raw)
To: pgsql-performance
Hi List,
Can anybody help me out with this -
is autovacuum similar to vacuum full analyse verbose.
--
Regards
Gauri
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Vacuum v/s Autovacuum
@ 2007-01-18 13:31 Michael Glaesemann <grzm@seespotcode.net>
parent: Gauri Kanekar <meetgaurikanekar@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Michael Glaesemann @ 2007-01-18 13:31 UTC (permalink / raw)
To: Gauri Kanekar <meetgaurikanekar@gmail.com>; +Cc: pgsql-performance
On Jan 18, 2007, at 22:24 , Gauri Kanekar wrote:
> is autovacuum similar to vacuum full analyse verbose.
http://www.postgresql.org/docs/8.2/interactive/routine-
vacuuming.html#AUTOVACUUM
Apparently, no FULL, no VERBOSE (which is only really useful if you
want to see the results, not for routine maintenance).
Michael Glaesemann
grzm seespotcode net
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Vacuum v/s Autovacuum
@ 2007-01-18 13:46 Gauri Kanekar <meetgaurikanekar@gmail.com>
parent: Michael Glaesemann <grzm@seespotcode.net>
0 siblings, 1 reply; 5+ messages in thread
From: Gauri Kanekar @ 2007-01-18 13:46 UTC (permalink / raw)
To: Michael Glaesemann <grzm@seespotcode.net>; +Cc: pgsql-performance
Hi
Thanks.
We have autovacuum ON , but still postgres server warns to
increas max_fsm_pages value.
Do autovacuum release space after it is over?
so how can we tackle it.
On 1/18/07, Michael Glaesemann <grzm@seespotcode.net> wrote:
>
>
> On Jan 18, 2007, at 22:24 , Gauri Kanekar wrote:
>
> > is autovacuum similar to vacuum full analyse verbose.
>
> http://www.postgresql.org/docs/8.2/interactive/routine-
> vacuuming.html#AUTOVACUUM
>
> Apparently, no FULL, no VERBOSE (which is only really useful if you
> want to see the results, not for routine maintenance).
>
>
> Michael Glaesemann
> grzm seespotcode net
>
>
>
--
Regards
Gauri
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Vacuum v/s Autovacuum
@ 2007-01-18 14:05 Bill Moran <wmoran@collaborativefusion.com>
parent: Gauri Kanekar <meetgaurikanekar@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Bill Moran @ 2007-01-18 14:05 UTC (permalink / raw)
To: Gauri Kanekar <meetgaurikanekar@gmail.com>; +Cc: Michael Glaesemann <grzm@seespotcode.net>; pgsql-performance
In response to "Gauri Kanekar" <meetgaurikanekar@gmail.com>:
> On 1/18/07, Michael Glaesemann <grzm@seespotcode.net> wrote:
> >
> > On Jan 18, 2007, at 22:24 , Gauri Kanekar wrote:
> >
> > > is autovacuum similar to vacuum full analyse verbose.
> >
> > http://www.postgresql.org/docs/8.2/interactive/routine-
> > vacuuming.html#AUTOVACUUM
> >
> > Apparently, no FULL, no VERBOSE (which is only really useful if you
> > want to see the results, not for routine maintenance).
[please don't top-post]
Actually, you can raise the debugging level in PostgreSQL and get something
similar to VERBOSE. The only problem is that it also increases the amount
of logging that occurs with everything.
> We have autovacuum ON , but still postgres server warns to
> increas max_fsm_pages value.
>
> Do autovacuum release space after it is over?
Yes.
If you're still getting warnings about max_fsm_pages while autovac is
running, you need to do one of two things:
1) Increase max_fsm_pages
2) Adjust autovacuum's settings so it vacuums more often.
Depending on this, you may also need to temporarily adjust max_fsm_pages,
then manually vacuum -- you may then find that autovacuum can keep everything
clean with lower settings of max_fsm_pages.
Overall, the best settings for 1 and 2 depend on the nature of your
workload, and simulation and monitoring will be required to find the
best values. I feel that the docs on this are very good. If the
amount of data that changes between runs of autovacuum is greater
than max_fsm_pages, then vacuum will be unable to reclaim all the
space.
--
Bill Moran
Collaborative Fusion Inc.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Vacuum v/s Autovacuum
@ 2007-01-18 14:14 Shoaib Mir <shoaibmir@gmail.com>
parent: Bill Moran <wmoran@collaborativefusion.com>
0 siblings, 0 replies; 5+ messages in thread
From: Shoaib Mir @ 2007-01-18 14:14 UTC (permalink / raw)
To: Bill Moran <wmoran@collaborativefusion.com>; +Cc: Gauri Kanekar <meetgaurikanekar@gmail.com>; Michael Glaesemann <grzm@seespotcode.net>; pgsql-performance
You will need to properly tune the thresholds for VACUUM and ANALYZE in case
of autovacuuming process, so that you do not need to increase the
max_fsm_pages oftenly...
-------------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 1/18/07, Bill Moran <wmoran@collaborativefusion.com> wrote:
>
> In response to "Gauri Kanekar" <meetgaurikanekar@gmail.com>:
> > On 1/18/07, Michael Glaesemann <grzm@seespotcode.net> wrote:
> > >
> > > On Jan 18, 2007, at 22:24 , Gauri Kanekar wrote:
> > >
> > > > is autovacuum similar to vacuum full analyse verbose.
> > >
> > > http://www.postgresql.org/docs/8.2/interactive/routine-
> > > vacuuming.html#AUTOVACUUM
> > >
> > > Apparently, no FULL, no VERBOSE (which is only really useful if you
> > > want to see the results, not for routine maintenance).
>
> [please don't top-post]
>
> Actually, you can raise the debugging level in PostgreSQL and get
> something
> similar to VERBOSE. The only problem is that it also increases the amount
> of logging that occurs with everything.
>
> > We have autovacuum ON , but still postgres server warns to
> > increas max_fsm_pages value.
> >
> > Do autovacuum release space after it is over?
>
> Yes.
>
> If you're still getting warnings about max_fsm_pages while autovac is
> running, you need to do one of two things:
> 1) Increase max_fsm_pages
> 2) Adjust autovacuum's settings so it vacuums more often.
>
> Depending on this, you may also need to temporarily adjust max_fsm_pages,
> then manually vacuum -- you may then find that autovacuum can keep
> everything
> clean with lower settings of max_fsm_pages.
>
> Overall, the best settings for 1 and 2 depend on the nature of your
> workload, and simulation and monitoring will be required to find the
> best values. I feel that the docs on this are very good. If the
> amount of data that changes between runs of autovacuum is greater
> than max_fsm_pages, then vacuum will be unable to reclaim all the
> space.
>
> --
> Bill Moran
> Collaborative Fusion Inc.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2007-01-18 14:14 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-01-18 13:24 Vacuum v/s Autovacuum Gauri Kanekar <meetgaurikanekar@gmail.com>
2007-01-18 13:31 ` Michael Glaesemann <grzm@seespotcode.net>
2007-01-18 13:46 ` Gauri Kanekar <meetgaurikanekar@gmail.com>
2007-01-18 14:05 ` Bill Moran <wmoran@collaborativefusion.com>
2007-01-18 14:14 ` Shoaib Mir <shoaibmir@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox