| From: | Robert Haas <robertmhaas(at)gmail(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:32:06 |
| Message-ID: | CA+TgmoYPBzirmugFwYctt0iLowJEDit4R5_PuF-=bsSspAEa+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 5, 2013 at 10:41 PM, abhinav batra <abbatra(at)gmail(dot)com> 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.
>
> So I wanted to know if someone is already working on this.
Not to my knowledge. But... I wonder why you want to work on this?
I've never heard of anyone having a performance problem because of
this. If you are, it would be interesting to hear the details.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-03-08 13:58:09 | Re: Index Unqiueness |
| Previous Message | Robert Haas | 2013-03-08 13:28:27 | Re: sql_drop Event Triggerg |