Skip site navigation (1) Skip section navigation (2)

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 05:04:08
Message-ID: CA+h6AhintbxXP3qDtu5T0AQNNjwSNDojFwuEnzy5i_B-sYe+_w@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Tue, Jul 3, 2012 at 10:19 AM, Raghavendra <
raghavendra(dot)rao(at)enterprisedb(dot)com> wrote:

>
> 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
>
>
Opps... correction in my query WHERE clause, it should be pointing to
relname not index -- >where relname=' input_transaction_snbs'   <--

--Raghav

In response to

Responses

pgsql-admin by date

Next:From: Samuel StearnsDate: 2012-07-03 07:18:11
Subject: Re: Duplicate Index Creation
Previous:From: RaghavendraDate: 2012-07-03 04:49:53
Subject: Re: Duplicate Index Creation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group