pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedsome databases have not been vacuumed ...
7+ messages / 6 participants
[nested] [flat]
* some databases have not been vacuumed ...
@ 2005-08-01 19:35 FM <dist-list@LEXUM.UMontreal.CA>
0 siblings, 1 reply; 7+ messages in thread
From: FM @ 2005-08-01 19:35 UTC (permalink / raw)
To: pgsql-admin
Hello after a vacuum full analyse I received this :
WARNING: some databases have not been vacuumed in 1805294030 transactions
HINT: Better vacuum them within 342189617 transactions, or you may have
a wraparound failure.
I read that it's because i do not vacuum DB very often.
Now I vacuum every night but the warning remains.
How can I get rid of this ?
Thanks !
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: some databases have not been vacuumed ...
@ 2005-08-01 19:44 Joshua D. Drake <jd@commandprompt.com>
parent: FM <dist-list@LEXUM.UMontreal.CA>
0 siblings, 2 replies; 7+ messages in thread
From: Joshua D. Drake @ 2005-08-01 19:44 UTC (permalink / raw)
To: FM <dist-list@LEXUM.UMontreal.CA>; +Cc: pgsql-admin
FM wrote:
> Hello after a vacuum full analyse I received this :
> WARNING: some databases have not been vacuumed in 1805294030 transactions
> HINT: Better vacuum them within 342189617 transactions, or you may have
> a wraparound failure.
>
> I read that it's because i do not vacuum DB very often.
> Now I vacuum every night but the warning remains.
> How can I get rid of this ?
Run a vacuum full on all the database.
>
> Thanks !
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: some databases have not been vacuumed ...
@ 2005-08-01 20:29 Gregory S. Williamson <gsw@globexplorer.com>
0 siblings, 0 replies; 7+ messages in thread
From: Gregory S. Williamson @ 2005-08-01 20:29 UTC (permalink / raw)
To: FM <dist-list@lexum.umontreal.ca>; pgsql-admin
Did you vacuum the template1 database as well as whatever databases you have created ?
HTH,
Greg Williamson
DBA
GlobeXplorer LLC
-----Original Message-----
From: pgsql-admin-owner@postgresql.org on behalf of FM
Sent: Mon 8/1/2005 12:35 PM
To: Mailing List Postgres-Admin
Cc:
Subject: [ADMIN] some databases have not been vacuumed ...
Hello after a vacuum full analyse I received this :
WARNING: some databases have not been vacuumed in 1805294030 transactions
HINT: Better vacuum them within 342189617 transactions, or you may have
a wraparound failure.
I read that it's because i do not vacuum DB very often.
Now I vacuum every night but the warning remains.
How can I get rid of this ?
Thanks !
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
!DSPAM:42ee7af1176271374616439!
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: some databases have not been vacuumed ...
@ 2005-08-01 20:51 FM <dist-list@LEXUM.UMontreal.CA>
parent: Joshua D. Drake <jd@commandprompt.com>
1 sibling, 1 reply; 7+ messages in thread
From: FM @ 2005-08-01 20:51 UTC (permalink / raw)
To: ; +Cc: pgsql-admin
I vacumm all DB ...except... postgres ones.
I"ll do a vacuum -all tonight
What is you vacuum strategy ?
vacuum everyday and vacuum full analyse ervery week ?
thanks !
Joshua D. Drake wrote:
> FM wrote:
>
>> Hello after a vacuum full analyse I received this :
>> WARNING: some databases have not been vacuumed in 1805294030
>> transactions
>> HINT: Better vacuum them within 342189617 transactions, or you may
>> have a wraparound failure.
>>
>> I read that it's because i do not vacuum DB very often.
>> Now I vacuum every night but the warning remains.
>> How can I get rid of this ?
>
>
> Run a vacuum full on all the database.
>
>>
>> Thanks !
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 3: Have you checked our extensive FAQ?
>>
>> http://www.postgresql.org/docs/faq
>
>
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: some databases have not been vacuumed ...
@ 2005-08-01 20:59 Scott Marlowe <smarlowe@g2switchworks.com>
parent: FM <dist-list@LEXUM.UMontreal.CA>
0 siblings, 0 replies; 7+ messages in thread
From: Scott Marlowe @ 2005-08-01 20:59 UTC (permalink / raw)
To: FM <dist-list@lexum.umontreal.ca>; +Cc: pgsql-admin
No. Vacuum full should not be necessary on a properly configured
server.
See:
http://www.postgresql.org/docs/8.0/static/maintenance.html
On Mon, 2005-08-01 at 15:51, FM wrote:
> I vacumm all DB ...except... postgres ones.
>
> I"ll do a vacuum -all tonight
>
> What is you vacuum strategy ?
> vacuum everyday and vacuum full analyse ervery week ?
>
> thanks !
>
>
> Joshua D. Drake wrote:
> > FM wrote:
> >
> >> Hello after a vacuum full analyse I received this :
> >> WARNING: some databases have not been vacuumed in 1805294030
> >> transactions
> >> HINT: Better vacuum them within 342189617 transactions, or you may
> >> have a wraparound failure.
> >>
> >> I read that it's because i do not vacuum DB very often.
> >> Now I vacuum every night but the warning remains.
> >> How can I get rid of this ?
> >
> >
> > Run a vacuum full on all the database.
> >
> >>
> >> Thanks !
> >>
> >> ---------------------------(end of broadcast)---------------------------
> >> TIP 3: Have you checked our extensive FAQ?
> >>
> >> http://www.postgresql.org/docs/faq
> >
> >
> >
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: some databases have not been vacuumed ...
@ 2005-08-02 14:28 Christopher Browne <cbbrowne@acm.org>
parent: Joshua D. Drake <jd@commandprompt.com>
1 sibling, 1 reply; 7+ messages in thread
From: Christopher Browne @ 2005-08-02 14:28 UTC (permalink / raw)
To: pgsql-admin
In an attempt to throw the authorities off his trail, jd@commandprompt.com ("Joshua D. Drake") transmitted:
> FM wrote:
>> Hello after a vacuum full analyse I received this :
>> WARNING: some databases have not been vacuumed in 1805294030 transactions
>> HINT: Better vacuum them within 342189617 transactions, or you may
>> have a wraparound failure.
>> I read that it's because i do not vacuum DB very often.
>> Now I vacuum every night but the warning remains.
>> How can I get rid of this ?
>
> Run a vacuum full on all the database.
That seems overkill.
The problem is likely that the "old tuples" are in some database not
being vacuumed. template1 is a likely candidate; do a plain VACUUM on
that and the message may go away.
It can be *possible* for the issue to be with template0, if it had at
some point been open for modification. If that is the case, it is a
good idea to:
- Unlock template0 (via table pg_database)
- Run VACUUM FREEZE on template0
- Relock it
--
(format nil "~S@~S" "cbbrowne" "gmail.com")
http://linuxdatabases.info/info/slony.html
"You think you know when you can learn, are more sure when you can
write, even more when you can teach, but certain when you can
program." -- Alan Perlis
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: some databases have not been vacuumed ...
@ 2005-08-02 17:08 Tom Lane <tgl@sss.pgh.pa.us>
parent: Christopher Browne <cbbrowne@acm.org>
0 siblings, 0 replies; 7+ messages in thread
From: Tom Lane @ 2005-08-02 17:08 UTC (permalink / raw)
To: Christopher Browne <cbbrowne@acm.org>; +Cc: pgsql-admin
Christopher Browne <cbbrowne@acm.org> writes:
> The problem is likely that the "old tuples" are in some database not
> being vacuumed. template1 is a likely candidate; do a plain VACUUM on
> that and the message may go away.
It's not really necessary to guess about which database(s) are
triggering the message: a quick look in pg_database will tell you.
See TFM:
http://www.postgresql.org/docs/8.0/static/maintenance.html#VACUUM-FOR-WRAPAROUND
regards, tom lane
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2005-08-02 17:08 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-08-01 19:35 some databases have not been vacuumed ... FM <dist-list@LEXUM.UMontreal.CA>
2005-08-01 19:44 ` Joshua D. Drake <jd@commandprompt.com>
2005-08-01 20:51 ` FM <dist-list@LEXUM.UMontreal.CA>
2005-08-01 20:59 ` Scott Marlowe <smarlowe@g2switchworks.com>
2005-08-02 14:28 ` Christopher Browne <cbbrowne@acm.org>
2005-08-02 17:08 ` Re: some databases have not been vacuumed ... Tom Lane <tgl@sss.pgh.pa.us>
2005-08-01 20:29 Re: some databases have not been vacuumed ... Gregory S. Williamson <gsw@globexplorer.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