Re: Should I keep INDEX on the table?

Also can somebody tell me the overhead involved in DROPing and CREATing
the indexes?
How often this activity should be performed?

-----Original Message-----
From: Rajan Bhide
Sent: Friday, May 14, 2004 3:27 PM
To: pgsql-novice(at)postgresql(dot)org; Tom Lane; Bruce Momjian
Subject: [NOVICE] Should I keep INDEX on the table?

Hello Forum,

I am having a table with UNIQUE constraints defined on three columns.
Also I have UNIQUE user defined INDEX with the same columns on the
table. The postgres documentation mentions that the user defined INDEX
is just the duplication if the table has PRIMARY Key or UNIQUE key
constraints with same columns.
http://www.postgresql.org/docs/7.4/static/indexes-unique.html

I require suggestion whether to keep the (duplicate?) used defined INDEX
on the table or remove it. The problem on removing the index is that my
table has almost 2M transtions in approx ~4 Hours and I need to perform
external reindexing (DROP and CREATE INDEX) every 2 Hours to reclaim the
dead space left behind by the deleted rows. If I remove the INDEX from
the table will my client work without performing external reindexing?

System Info:
SunOS firerunner 5.9 Generic_112233-01 sun4u sparc SUNW,UltraAX-i2
Memory size: 1024 Megabytes

Postgres Version : 7.4.1

Thanks,
Rajan Bhide

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html