From: | "John P(dot) Looney" <valen(at)tuatha(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | postgres <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Postgres db corrupted ? |
Date: | 2003-07-29 16:22:56 |
Message-ID: | 20030729162256.GA5304@magicbluesmoke.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Jul 29, 2003 at 10:38:50AM -0400, Tom Lane mentioned:
> A quick-and-dirty nostrum that sometimes helps for this sort of thing
> is "vacuum full pg_database". (The idea is to get rid of dead tuples
> that a new backend might be accidentally picking instead of the live
> ones --- it has to read pg_database before it's joined the PROC array,
> which among other things means it can't tell 100% accurately which rows
> are really committed.)
Ah, OK. That's the sort of help I was hoping to get. Alas, for very
different reasons (I'd run out of ideas), I'd run that myself, with no
gain.
> If no go, could we see the output of "select * from pg_database"?
Yep, no worries...
postgres=# select * from pg_database;
datname | datdba | encoding | datistemplate | datallowconn | datlastsysoid | datvacuumxid | datfrozenxid | datpath
-----------------+--------+----------+---------------+--------------+---------------+--------------+--------------+---------
pguser | | 0 | f | t | 16554 | 611746 | 3221837219 |
phpuser-654937 | | 0 | f | t | 16554 | 611746 | 3221837219 |
gestr-654937 | | 0 | f | t | 16554 | 611746 | 3221837219 |
template0 | 1 | 0 | t | f | 16554 | 49 | 49 |
postgres | 1 | 0 | f | t | 16554 | 658793 | 658793 |
rob-654937 | | 0 | f | t | 16554 | 611746 | 3221837219 |
template1 | 1 | 0 | t | t | 16554 | 611746 | 3221837219 |
testtest | 28 | 0 | f | t | 16554 | 49 | 49 |
dsitestogo | 33 | 0 | f | t | 16554 | 49 | 49 |
bb1 | 36 | 0 | f | t | 16554 | 49 | 49 |
carlstest | 37 | 0 | f | t | 16554 | 49 | 49 |
pgdbase | 38 | 0 | f | t | 16554 | 49 | 49 |
novadance | 41 | 0 | f | t | 16554 | 49 | 49 |
MyPgSQLTest | 43 | 0 | f | t | 16554 | 49 | 49 |
forum | 45 | 0 | f | t | 16554 | 49 | 49 |
ct2 | 48 | 0 | f | t | 16554 | 49 | 49 |
directory | 49 | 0 | f | t | 16554 | 49 | 49 |
faqsection | 50 | 0 | f | t | 16554 | 49 | 49 |
demo | 51 | 0 | f | t | 16554 | 49 | 49 |
planetepochdb | 53 | 0 | f | t | 16554 | 49 | 49 |
bbadmin | | 0 | f | t | 16554 | 49 | 49 |
shanecody | | 0 | f | t | 16554 | 49 | 49 |
dmduffy-654937 | | 0 | f | t | 16554 | 49 | 49 |
zozallen-665478 | | 0 | f | t | 16554 | 49 | 49 |
zozhugh-665478 | | 0 | f | t | 16554 | 49 | 49 |
zozea | 41 | 0 | f | t | 16554 | 49 | 49 |
(26 rows)
John
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-07-29 16:55:04 | Re: Postgres db corrupted ? |
Previous Message | Ragnar Kjrstad | 2003-07-29 15:16:11 | Re: Replication/Failover/HA solution |