Re: 8.1.8 autovacuum missing databases

Ian Westmacott <ianw@[EMAIL PROTECTED]
> writes:
> itvtrackdata=> select ctid,xmin,* from pg_database;
>  ctid  |   xmin   |     datname      | datdba | encoding | datistemplate
| datallowconn | datconnlimit | datlastsysoid | datvacuumxid | datfrozenxid
| dattablespace | datconfig |         datacl
>
-------+----------+------------------+--------+----------+---------------+--------------+--------------+---------------+--------------+--------------+---------------+-----------+------------------------
>  (0,1) |      564 | postgres         |     10 |        6 | f            
| t            |           -1 |         10792 |          499 |          499
|          1663 |           |
>  (0,2) |      577 | itvtrackdata     |  16384 |        6 | f            
| t            |           -1 |         10792 |          499 |          499
|          1663 |           |
>  (0,3) |      605 | itvtrackdatauser |  16384 |        6 | f            
| t            |           -1 |         10792 |          499 |          499
|          1663 |           |
>  (0,5) | 18350176 | itvtrackdatapos  |  16384 |        6 | f            
| t            |           -1 |         10792 |          499 |          499
|          1663 |           |
>  (0,6) |      557 | template1        |     10 |        6 | t            
| t            |           -1 |         10792 |          499 |          499
|          1663 |           | {postgres=CT/postgres}
>  (0,7) |      558 | template0        |     10 |        6 | t            
| f            |           -1 |         10792 |          499 |          499
|          1663 |           | {postgres=CT/postgres}
> (6 rows)

499 is the value that those columns would have immediately after initdb,
in an 8.1 database.  So what this says is that vacuum has never
succeeded in updating the values at all, in any of your databases.
It definitely *should* be doing that given the size of the age() values
you're re****ting.  Moreover, after a look through the 8.1.8 source code
I cannot see how it would not update the values without throwing an
ERROR or at least a WARNING into the postmaster log.  (What have you got
log_min_messages set to, anyway?  Maybe the complaint is getting
suppressed?)

			regards, tom lane

-- 
Sent via pgsql-admin mailing list (pgsql-admin@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin