pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedVacuumdb
8+ messages / 7 participants
[nested] [flat]
* Vacuumdb
@ 2003-04-02 09:46 Raquel Vieira <raquel.vieira@ent.efacec.pt>
0 siblings, 0 replies; 8+ messages in thread
From: Raquel Vieira @ 2003-04-02 09:46 UTC (permalink / raw)
To: pgsql-admin
I'm using PostgreSQL 7.0.3.
I'm doing vacuumdb in my database every night to repair it. But now I have a
problem. I'm looking in /var/lib/pgsql/data/base/ for the tables length and
the primary keys of the tables are not cleaned and is increasing evey day.
What can I do to clean it?
Thank you for the help.
Raquel Vieira
^ permalink raw reply [nested|flat] 8+ messages in thread
* Vacuumdb
@ 2003-04-02 15:51 Raquel Vieira <raquel.vieira@ent.efacec.pt>
2003-04-03 05:13 ` Re: Vacuumdb A.Bhuvaneswaran <bhuvansql@myrealbox.com>
0 siblings, 1 reply; 8+ messages in thread
From: Raquel Vieira @ 2003-04-02 15:51 UTC (permalink / raw)
To: pgsql-admin
I'm using PostgreSQL 7.0.3.
I'm doing vacuumdb in my database every night to repair it. But now I have a
problem. I'm looking in /var/lib/pgsql/data/base/ for the tables length and
the primary keys of the tables are not cleaned and is increasing evey day.
What can I do to clean it?
Thank you for the help.
Raquel Vieira
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Vacuumdb
2003-04-02 15:51 Vacuumdb Raquel Vieira <raquel.vieira@ent.efacec.pt>
@ 2003-04-03 05:13 ` A.Bhuvaneswaran <bhuvansql@myrealbox.com>
2003-04-03 19:22 ` Re: Vacuumdb Robert Treat <xzilla@users.sourceforge.net>
0 siblings, 1 reply; 8+ messages in thread
From: A.Bhuvaneswaran @ 2003-04-03 05:13 UTC (permalink / raw)
To: Raquel Vieira <raquel.vieira@ent.efacec.pt>; +Cc: pgsql-admin
> I'm using PostgreSQL 7.0.3.
> I'm doing vacuumdb in my database every night to repair it. But now I have a
> problem. I'm looking in /var/lib/pgsql/data/base/ for the tables length and
> the primary keys of the tables are not cleaned and is increasing evey day.
> What can I do to clean it?
> Thank you for the help.
If you mean hard disk space consumption, you might have to run vacuum
full.
regards,
bhuvaneswaran
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Vacuumdb
2003-04-02 15:51 Vacuumdb Raquel Vieira <raquel.vieira@ent.efacec.pt>
2003-04-03 05:13 ` Re: Vacuumdb A.Bhuvaneswaran <bhuvansql@myrealbox.com>
@ 2003-04-03 19:22 ` Robert Treat <xzilla@users.sourceforge.net>
0 siblings, 0 replies; 8+ messages in thread
From: Robert Treat @ 2003-04-03 19:22 UTC (permalink / raw)
To: A.Bhuvaneswaran <bhuvansql@myrealbox.com>; +Cc: Raquel Vieira <raquel.vieira@ent.efacec.pt>; pgsql-admin
On Thu, 2003-04-03 at 00:13, A.Bhuvaneswaran wrote:
> > I'm using PostgreSQL 7.0.3.
> > I'm doing vacuumdb in my database every night to repair it. But now I have a
> > problem. I'm looking in /var/lib/pgsql/data/base/ for the tables length and
> > the primary keys of the tables are not cleaned and is increasing evey day.
> > What can I do to clean it?
> > Thank you for the help.
>
> If you mean hard disk space consumption, you might have to run vacuum
> full.
>
Actually the vacuum in 7.0.3 is a vacuum full. I'm guessing the problem
is really index bloat, try dropping and recreating some of your indexes.
After that you need to seriously look at upgrading.
Robert Treat
^ permalink raw reply [nested|flat] 8+ messages in thread
* Vacuumdb
@ 2004-10-08 18:24 Pallav Kalva <pkalva@deg.cc>
0 siblings, 0 replies; 8+ messages in thread
From: Pallav Kalva @ 2004-10-08 18:24 UTC (permalink / raw)
To: pgsql-admin
Hi Everybody,
If i do vacuumdb -z <databasename> daily as a part of my
maintanence, do i have to still vacuum analyze each table in the
database ?. The reason i am asking is that even though i do vacuumdb
daily my stats are not updated properly in pg_class view and the
reltuples values is much higher than the actual records in the table ?
can anyone shed some light on this problem ?
Thanks!
Pallav
^ permalink raw reply [nested|flat] 8+ messages in thread
* vacuumdb
@ 2006-02-13 16:42 Juliano <juliano.listas@gmail.com>
2006-02-13 17:46 ` Re: vacuumdb Jim C. Nasby <jnasby@pervasive.com>
2006-02-13 20:41 ` Re: vacuumdb Guido Barosio <gbarosio@gmail.com>
0 siblings, 2 replies; 8+ messages in thread
From: Juliano @ 2006-02-13 16:42 UTC (permalink / raw)
To: pgsql-admin
Hi all,
There is a way to see vacuumdb last running ?
tks
--
Juliano
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: vacuumdb
2006-02-13 16:42 vacuumdb Juliano <juliano.listas@gmail.com>
@ 2006-02-13 17:46 ` Jim C. Nasby <jnasby@pervasive.com>
1 sibling, 0 replies; 8+ messages in thread
From: Jim C. Nasby @ 2006-02-13 17:46 UTC (permalink / raw)
To: juliano.gaio@gmail.com; +Cc: pgsql-admin
On Mon, Feb 13, 2006 at 01:42:06PM -0300, Juliano wrote:
> Hi all,
>
> There is a way to see vacuumdb last running ?
If you mean you'd like to know when a vacuum was last run on a table,
sadly, there is no way. Though if you're using 8.1 and have autovacuum
enabled there may be some way to see when it last vacuumed something.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: vacuumdb
2006-02-13 16:42 vacuumdb Juliano <juliano.listas@gmail.com>
@ 2006-02-13 20:41 ` Guido Barosio <gbarosio@gmail.com>
1 sibling, 0 replies; 8+ messages in thread
From: Guido Barosio @ 2006-02-13 20:41 UTC (permalink / raw)
To: juliano.gaio@gmail.com; +Cc: pgsql-admin
Hmmm, AFAIK no, but you can get the age of the databases, and guess if you
need to issue a vacuum or not.
quote from the documentation (www.postgresql.org -> documentation):
SELECT datname, age(datfrozenxid) FROM pg_database;
The age column measures the number of transactions from the cutoff XID to
the current transaction's XID.
With the standard freezing policy, the age column will start at one billion
for a freshly-vacuumed database. When the age approaches two billion, the
database must be vacuumed again to avoid risk of wraparound
failures.Recommended practice is to vacuum
each database at least once every half-a-billion (500 million)
transactions,so as to provide plenty of safety margin. To help meet
this rule, each
database-wide VACUUM automatically delivers a warning if there are any
pg_database entries showing an age of more than 1.5 billion transactions,
for example:
play=# VACUUM;
WARNING: some databases have not been vacuumed in 1613770184 transactions
HINT: Better vacuum them within 533713463 transactions, or you may
have a wraparound failure.
VACUUM
Best regards,
Guido
On 2/13/06, Juliano <juliano.listas@gmail.com> wrote:
>
> Hi all,
>
> There is a way to see vacuumdb last running ?
>
> tks
>
> --
> Juliano
--
/"\ ASCII Ribbon Campaign .
\ / - NO HTML/RTF in e-mail .
X - NO Word docs in e-mail .
/ \ -----------------------------------------------------------------
^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2006-02-13 20:41 UTC | newest]
Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-04-02 09:46 Vacuumdb Raquel Vieira <raquel.vieira@ent.efacec.pt>
2003-04-02 15:51 Vacuumdb Raquel Vieira <raquel.vieira@ent.efacec.pt>
2003-04-03 05:13 ` A.Bhuvaneswaran <bhuvansql@myrealbox.com>
2003-04-03 19:22 ` Robert Treat <xzilla@users.sourceforge.net>
2004-10-08 18:24 Vacuumdb Pallav Kalva <pkalva@deg.cc>
2006-02-13 16:42 vacuumdb Juliano <juliano.listas@gmail.com>
2006-02-13 17:46 ` Re: vacuumdb Jim C. Nasby <jnasby@pervasive.com>
2006-02-13 20:41 ` Re: vacuumdb Guido Barosio <gbarosio@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