| From: | "suhas(dot)basavaraj12" <suhas(dot)b(at)verse(dot)in> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | CREATING INDEX on column having null values |
| Date: | 2012-12-05 08:10:10 |
| Message-ID: | 1354695010903-5735127.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi,
I have a partitioned table(partitioned on date) .There are about 1 million
insertions per day. There is a column called mess_id. This column is updated
.But update query is taking huge time.When i checked , this column is not
unique, and most of the time its having null . Say everyday out of 1
million only 20K rows are not null for this column ;.Insertions are
happening very fast , but update is very slow.
How to optimize my update query? Is it good to create index on that
column .. i m worried about my insertions getting slow
Rgrds
Suhas
--
View this message in context: http://postgresql.1045698.n5.nabble.com/CREATING-INDEX-on-column-having-null-values-tp5735127.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Willem Leenen | 2012-12-05 08:47:42 | Re: CREATING INDEX on column having null values |
| Previous Message | Jeff Janes | 2012-12-04 23:42:21 | Re: Slow query: bitmap scan troubles |