[ADMIN] Duplicate Index Creation

2012-07-02 Thread Samuel Stearns
Howdy, Environment: Postgres 8.4.7 64-bit Solaris 10 I create an index as: CREATE INDEX i1 ON input_transaction_snbs USING btree (trans_client); which is creating a 2nd duplicate index in error as this query shows: SELECT idstat.relname AS table_name, idstat.indexrelname AS index

Re: [ADMIN] Duplicate Index Creation

2012-07-02 Thread Raghavendra
> > > which is creating a 2nd duplicate index in error as this query shows: > > ** > Hmm,,, that's strange.. Can you update with the output of the below command. \d input_transaction_snbs --- Regards, Raghavendra EnterpriseDB Corporation Blog: http://raghavt.blogspot.com/

Re: [ADMIN] Duplicate Index Creation

2012-07-02 Thread Tom Lane
Samuel Stearns writes: > I create an index as: ... > which is creating a 2nd duplicate index in error as this query shows: > SELECT idstat.relname AS table_name, >idstat.indexrelname AS index_name, >idstat.idx_scan AS times_used, >pg_size_pretty(pg_relation_size(idstat.rel

Re: [ADMIN] Duplicate Index Creation

2012-07-02 Thread Samuel Stearns
I get the duplicate entries. Also, if I do not limit that query to input_transaction_snbs and run it against everything, input_transaction_snbs is the only table that shows up with duplicate entries. Sam -Original Message- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: Tuesday, 3

Re: [ADMIN] Duplicate Index Creation

2012-07-02 Thread Raghavendra
On Tue, Jul 3, 2012 at 9:25 AM, Samuel Stearns 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 = > '

Re: [ADMIN] Duplicate Index Creation

2012-07-02 Thread Raghavendra
On Tue, Jul 3, 2012 at 10:19 AM, Raghavendra < raghavendra@enterprisedb.com> wrote: > > On Tue, Jul 3, 2012 at 9:25 AM, Samuel Stearns > wrote: > >> Results of \d (without all the column defs): >> >> Indexes: >> "input_transaction_snbs_prod_pkey" PRIMARY KEY, btree (id) >> "i1" btree

Re: [ADMIN] Duplicate Index Creation

2012-07-03 Thread Samuel Stearns
012 2:34 PM To: Samuel Stearns Cc: Tom Lane; pgsql-admin@postgresql.org Subject: Re: [ADMIN] Duplicate Index Creation On Tue, Jul 3, 2012 at 10:19 AM, Raghavendra mailto:raghavendra@enterprisedb.com>> wrote: On Tue, Jul 3, 2012 at 9:25 AM, Samuel Stearns mailto:sstea...@internode.co

Re: [ADMIN] Duplicate Index Creation

2012-07-03 Thread Raghavendra
On Tue, Jul 3, 2012 at 12:48 PM, Samuel Stearns wrote: > Before and after analyze: > > ** ** > > select schemaname,relid,indexrelid,relname,indexrelname from > > pg_stat_all_indexes where relname='input_transaction_snbs'; > > ** ** > > schemaname | relid | indexrelid |reln

Re: [ADMIN] Duplicate Index Creation

2012-07-03 Thread Samuel Stearns
he db why is it that input_transaction_snbs is the only one that returns duplicates from the original query? Sam From: Raghavendra [mailto:raghavendra@enterprisedb.com] Sent: Wednesday, 4 July 2012 12:46 AM To: Samuel Stearns Cc: Tom Lane; pgsql-admin@postgresql.org Subject: Re: [ADMIN] Duplicate Index Cre

Re: [ADMIN] Duplicate Index Creation

2012-07-03 Thread Raghavendra
On Wed, Jul 4, 2012 at 7:09 AM, Samuel Stearns wrote: > Ok, that returns only the 1 row: > > ** ** > > SELECT idstat.indexrelid as indexrelid, > >idstat.schemaname AS schema_name, > >idstat.relname AS table_name, > >idstat.indexrelname AS index_name, >

Re: [ADMIN] Duplicate Index Creation

2012-07-08 Thread Samuel Stearns
'though I had it limited to input_transaction_snbs. Anyway, all good now. Thanks again. From: Raghavendra [mailto:raghavendra@enterprisedb.com] Sent: Wednesday, 4 July 2012 2:31 PM To: Samuel Stearns Cc: Tom Lane; pgsql-admin@postgresql.org Subject: Re: [ADMIN] Duplicate Index Creatio