Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id DA8AF9FC268 for ; Tue, 30 Oct 2007 16:21:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 01265-03 for ; Tue, 30 Oct 2007 16:21:10 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from outbound-mail-52.bluehost.com (outbound-mail-52.bluehost.com [69.89.20.32]) by postgresql.org (Postfix) with SMTP id B92169FC29B for ; Tue, 30 Oct 2007 16:21:09 -0300 (ADT) Received: (qmail 11793 invoked by uid 0); 30 Oct 2007 19:21:07 -0000 Received: from unknown (HELO box54.bluehost.com) (69.89.20.54) by mailproxy3.bluehost.com with SMTP; 30 Oct 2007 19:21:07 -0000 Received: from corp.messageone.com ([66.219.55.2] helo=[10.0.51.109]) by box54.bluehost.com with esmtp (Exim 4.68) (envelope-from ) id 1ImweB-00029u-1y for pgsql-admin@postgresql.org; Tue, 30 Oct 2007 13:21:07 -0600 From: Kevin Kempter To: pgsql-admin@postgresql.org Subject: another transaction ID question: Date: Tue, 30 Oct 2007 13:16:00 -0600 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-01=_wL4JHTdJhoO/E/f" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710301316.00339.kevin@kevinkempterllc.com> X-Identified-User: {840:box54.bluehost.com:kevinkem:kevinkempterllc.com} {sentby:bopbeforesmtp 66.219.55.2 authed with kevinkempterllc.com} X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.242 tagged_above=0 required=5 tests=AWL=-0.704, BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200710/309 X-Sequence-Number: 27223 --Boundary-01=_wL4JHTdJhoO/E/f Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi All; In addition to bumping up the max_fsm_pages value, I'm preparing to run a full db vacuum to avoid a transaction ID wrap-around failure for an 8.1.4 server. (we do have autovacuum on, and we're using the 8.2 defaults). I'm doing this based on a recent message from a regular vacuum verbose of the postgres db: CPU 0.00s/0.00u sec elapsed 0.00 sec. INFO: free space map contains 7464818 pages in 502 relations DETAIL: A total of 7500000 page slots are in use (including overhead). 19269120 page slots are required to track all free space. Current limits are: 7500000 page slots, 1000 relations, using 44010 KB. NOTICE: number of page slots needed (19269120) exceeds max_fsm_pages (7500000) HINT: Consider increasing the configuration parameter "max_fsm_pages" to a value over 19269120. WARNING: database "emsam-1" must be vacuumed within 432563175 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "emsam-1". VACUUM I'm looking at the pg_database table like so: postgres=# select datname, age(datfrozenxid) from pg_database; datname | age -----------+------------ postgres | 1073744186 emsam-1 | 1714922745 template1 | 629788508 template0 | 1961232297 (4 rows) I see that template0 is closer than any other db to the 2Billion mark. Of course if I try and connect to template0 I get this: \c template0 FATAL: database "template0" is not currently accepting connections Previous connection kept postgres=# Do I need to vacuum template0 ? If so, how to I alter perms so I can connect to it ? Thanks in nadvance.. /Kevin --Boundary-01=_wL4JHTdJhoO/E/f Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

Hi All;

In addition to bumping up the max_fsm_pages value, I'm preparing to run a full db vacuum to avoid a transaction ID wrap-around failure for an 8.1.4 server. (we do have autovacuum on, and we're using the 8.2 defaults). I'm doing this based on a recent message from a regular vacuum verbose of the postgres db:

CPU 0.00s/0.00u sec elapsed 0.00 sec.

INFO: free space map contains 7464818 pages in 502 relations

DETAIL: A total of 7500000 page slots are in use (including overhead).

19269120 page slots are required to track all free space.

Current limits are: 7500000 page slots, 1000 relations, using 44010 KB.

NOTICE: number of page slots needed (19269120) exceeds max_fsm_pages (7500000)

HINT: Consider increasing the configuration parameter "max_fsm_pages" to a value over 19269120.

WARNING: database "emsam-1" must be vacuumed within 432563175 transactions

HINT: To avoid a database shutdown, execute a full-database VACUUM in "emsam-1".

VACUUM

I'm looking at the pg_database table like so:

postgres=# select datname, age(datfrozenxid) from pg_database;

datname | age

-----------+------------

postgres | 1073744186

emsam-1 | 1714922745

template1 | 629788508

template0 | 1961232297

(4 rows)

I see that template0 is closer than any other db to the 2Billion mark.

Of course if I try and connect to template0 I get this:

\c template0

FATAL: database "template0" is not currently accepting connections

Previous connection kept

postgres=#

Do I need to vacuum template0 ?

If so, how to I alter perms so I can connect to it ?

Thanks in nadvance..

/Kevin

--Boundary-01=_wL4JHTdJhoO/E/f--