| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> | 
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
| Cc: | pgsql-hackers(at)postgresql(dot)org | 
| Subject: | Re: Performance-improvement idea: shortcircuit unique-index checks | 
| Date: | 2001-02-19 21:12:43 | 
| Message-ID: | 200102192112.QAA02073@candle.pha.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
> I'm not quite sure how to implement this, but I wanted to toss the idea
> out for discussion.  Probably we'd have to have some cooperation between
> the heap_update level (where the fact that it's an update is known, and
> where we'd have a chance to test for changes in particular columns) and
> the index access level.  Maybe it's wrong for the index access level to
> have primary responsibility for uniqueness checks in the first place.
> 
> Obviously this isn't going to happen for 7.1, but it might make a nice
> performance improvement for 7.2.
Seems a better solution would be to put a 'deleted' bit in the index so
we would have to visit those heap tuples only once for a committed
status.  Similar to what we do with heap tuples so we don't have to
visit pg_log repeatedly.
-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-02-19 21:21:29 | Re: Performance-improvement idea: shortcircuit unique-index checks | 
| Previous Message | Tom Lane | 2001-02-19 20:59:46 | Performance-improvement idea: shortcircuit unique-index checks |