From: | "Chris White" <cjwhite(at)cisco(dot)com> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Duplicate indexes found in the postgres Database |
Date: | 2003-02-05 22:47:11 |
Message-ID: | 00df01c2cd68$85a06750$ff926b80@amer.cisco.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tom,
User was able to recreate the problem, but this time only on table got
duplicated 'gui_config'. So here is the info you wanted:
select ctid,xmin,xmax,oid,* from pg_class where relname = 'gui_config';
ctid | xmin | xmax | oid | relname | reltype | relowner | relam |
relfilenode | relpages | reltuples | reltoastrelid | reltoastidxid |
relhasindex | relisshared | relkind | relnatts | relchecks | reltriggers |
relukeys | relfkeys | relrefs | relhasoids | relhaspkey | relhasrules |
relhassubclass | relacl
--------+------+------+-------+------------+---------+----------+-------+---
----------+----------+-----------+---------------+---------------+----------
---+-------------+---------+----------+-----------+-------------+----------+
----------+---------+------------+------------+-------------+---------------
-+-----------------------
(2,54) | 176 | 191 | 16560 | gui_config | 16561 | 101 | 0 |
16560 | 10 | 1000 | 0 | 0 | t |
f | r | 2 | 0 | 0 | 0 |
0 | 0 | t | t | f | f |
{=,aesop_gui=arwdRxt}
(2,56) | 191 | 206 | 16560 | gui_config | 16561 | 101 | 0 |
16560 | 10 | 1000 | 0 | 0 | t |
f | r | 2 | 0 | 0 | 0 |
0 | 0 | t | t | f | f |
{=,aesop_gui=arwdRxt}
(2 rows)
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Saturday, February 01, 2003 12:42 PM
To: Chris White
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Duplicate indexes found in the postgres Database
"Chris White" <cjwhite(at)cisco(dot)com> writes:
> How do I look at the catalogs and which ones do I need to look at?
Now that I look at it, pg_tables is not a join in 7.2, but just a
straight select from pg_class. So the problem is definitely in
pg_class. Let's see the results of
select ctid,xmin,xmax,oid,* from pg_class where relname = 'vm_message';
and similarly for the other duplicates.
> No we haven't seen any system crashes, but people have reported that the
> tables that are duplicated are possibly missing some data.
Hm. Trying to avoid theorizing in advance of the data...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ian Burrell | 2003-02-05 23:15:50 | Re: pg_restore problem with 7.3.1 |
Previous Message | Chris White | 2003-02-05 22:33:13 | Re: Duplicate indexes found in the postgres Database |