| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | abhinav batra <abbatra(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Index Unqiueness |
| Date: | 2013-03-08 13:58:09 |
| Message-ID: | 20130308135809.GA24484@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-03-06 09:11:38 +0530, abhinav batra wrote:
> Hey
> I want to work towards the follwing feature in TODO list:
> Prevent index uniqueness checks when UPDATE does not modify the
> columnUniqueness
> (index) checks are done when updating a column even if the column is not
> modified by the UPDATE. However, HOT already short-circuits this in common
> cases, so more work might not be helpful.
I'd be interested in something slightly related that is doing HOT on a
per-index basis. Currently we don't do hot if any index is updated even
though quite possibly most of the indexes don't change.
I think that might result in some quite nice speedups...
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-03-08 14:11:55 | Re: Materialized views WIP patch |
| Previous Message | Robert Haas | 2013-03-08 13:32:06 | Re: Index Unqiueness |