Re: Duplicate Index Creation

From: Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com>
To: Samuel Stearns <SStearns(at)internode(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Duplicate Index Creation
Date: 2012-07-03 04:49:53
Message-ID: CA+h6AhgZr7Qj4jyP5evg+ABHPpAEsVwfTCaKsGNktRvSrwcYbw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Jul 3, 2012 at 9:25 AM, Samuel Stearns <SStearns(at)internode(dot)com(dot)au>wrote:

> Results of \d (without all the column defs):
>
> Indexes:
> "input_transaction_snbs_prod_pkey" PRIMARY KEY, btree (id)
> "i1" btree (trans_client)
> Check constraints:
> "chk_charge" CHECK (charge_type IS NULL OR charge_type =
> 'Recurring'::text OR charge_type = 'Usage'::text OR charge_type =
> 'Fee'::text OR charge_type = 'Equipment'::text OR charge_type = 'One-t
> ime'::text OR charge_type = 'Reversal'::text OR charge_type =
> 'Adjustment'::text)
>
> Thanks. I was checking any INVALID indexes on the table. Its fine, can try
below query.

select schemaname,relid,indexrelid,relname,indexrelname from
pg_stat_all_indexes where relname='i1';

Also, try to ANALYZE the database and retry the queries. Its just to
confirm that query results are getting from updated catalogs.

--Raghav

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Raghavendra 2012-07-03 05:04:08 Re: Duplicate Index Creation
Previous Message Samuel Stearns 2012-07-03 03:55:52 Re: Duplicate Index Creation