Performance Improvement for Unique Indexes - Mailing list pgsql-hackers

From Gokulakannan Somasundaram
Subject Performance Improvement for Unique Indexes
Date
Msg-id 9362e74e1003240417x26031e24u7c4da37dd0a51014@mail.gmail.com
Whole thread Raw
Responses Re: Performance Improvement for Unique Indexes
List pgsql-hackers
Hi,<br />   While i was studying the unique index checks very closely, i realized that what we need is to find out
whetherthe tuple is deleted / not. So say a tuple is deleted by a transaction, but it is not dead( because of some long
runningtransaction ), still we can mark a hint bit as deleted and it will help the subsequent transactions doing the
uniquechecks. As a matter of fact, it will help the deferred_unique cases, since it will anyway check the tuples twice,
ifthere is a duplicate.<br />    So we have one bit left in the Index Tuple that can be used as hint bit. If we are
readyto break the disk compatibility, then we can store the size as a multiple of 8, and we will get three bits free.
Anycomments?<br /><br />Thanks,<br />Gokul.<br /> 

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [COMMITTERS] pgsql: Add connection messages for streaming replication.
Next
From: Heikki Linnakangas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Add connection messages for streaming replication.