X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 3A3AC53D6E for ; Thu, 10 Mar 2005 16:45:52 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 83899-01 for ; Thu, 10 Mar 2005 16:45:42 +0000 (GMT) Received: from mail.securax.org (mail.securax.org [212.123.25.145]) by svr1.postgresql.org (Postfix) with ESMTP id B600D564BF for ; Thu, 10 Mar 2005 16:45:40 +0000 (GMT) Received: (qmail 22260 invoked by uid 2077); 10 Mar 2005 16:42:12 -0000 Received: from scx (HELO ?10.3.3.12?) (milen@securax.org@scx) by mail.securax.org with SMTP; 10 Mar 2005 16:42:12 -0000 Message-ID: <423079B3.8050601@securax.org> Date: Thu, 10 Mar 2005 18:45:39 +0200 From: "Milen A. Radev" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Fuhr Cc: pgsql-admin@postgresql.org Subject: Re: Too frequent warnings for wraparound failure References: <42301107.6010901@securax.org> <20050310155734.GA86004@winnie.fuhr.org> In-Reply-To: <20050310155734.GA86004@winnie.fuhr.org> X-Enigmail-Version: 0.90.1.1 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.008 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/152 X-Sequence-Number: 16650 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Fuhr wrote: > On Thu, Mar 10, 2005 at 11:19:03AM +0200, Milen A. Radev wrote: > > >>exec /usr/local/pgsql/bin/vacuumdb -U postgres -h localhost \ >>- --all --analyze >>$PG_VACUUM_LOG 2>&1 > > > My first thought was that the lone hyphen at the beginning of the > script's last line might be causing an end of option processing, Well, that hyphen is inserted by Enigmail, so it's not part of the actual script. Here it is again (hopefully not garbled): BEGIN------------------------------------------- #!/bin/sh # cron script to vacuum pgsql databases # PG_VACUUM_LOG=/var/log/pg_vacuum echo Starting at `date "+%Y-%m-%d %H:%M:%S"` >> $PG_VACUUM_LOG exec /usr/local/pgsql/bin/vacuumdb -U postgres \ -h localhost --all --analyze >>$PG_VACUUM_LOG 2>&1 END------------------------------------------- > but your output does show many databases being vacuumed (do all > databases appear in the real output?). However, I tried running Yes, they all appear in the log. > that script with several versions of PostgreSQL and vacuumdb failed > with a usage error in every case. Are you sure the script you > posted is the one that's running? What version of PostgreSQL are > you using? As Tom mentioned, what's the output of the following 7.4.7 on Debian GNU/Linux 3.0 (Woody)[Linux xxxx 2.6.10 #1 SMP Thu Feb 10 18:52:12 EET 2005 i686 unknown] > query? > > SELECT datname, age(datfrozenxid) FROM pg_database; > Two queries - 2 seconds apart: template1=# SELECT datname, age(datfrozenxid) FROM pg_database; datname | age - -----------+------------- xxx1 | 1519763573 xxx2 | 1519754033 xxx3 | 1519592503 template1 | 1517875932 template0 | -1808458730 xxx4 | 1517860620 xxx5 | 1517786431 xxx6 | 1517780441 xxx7 | 1517762875 xxx8 | 1517755876 xxx9 | 1517749309 xxx10 | 1516823602 (12 rows) template1=# SELECT datname, age(datfrozenxid) FROM pg_database; datname | age - -----------+------------- xxx1 | 1519769620 xxx2 | 1519760080 xxx3 | 1519598550 template1 | 1517881979 template0 | -1808452683 xxx4 | 1517866667 xxx5 | 1517792478 xxx6 | 1517786488 xxx7 | 1517768922 xxx8 | 1517761923 xxx9 | 1517755356 xxx10 | 1516829649 (12 rows) - -- Milen A. Radev -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCMHmzqGlhYx0/sboRAsEFAJ0RWe8XVtLWWiOOrt46Nwg9xBD4hgCePhP9 YyYfj2LsKUCIFeheS71iI44= =TDVO -----END PGP SIGNATURE-----