Tom Lane <t...@sss.pgh.pa.us> wrote: > Greg Stark <st...@enterprisedb.com> writes: >> ... Argh, sorry, as soon as I hit send I realized this is wrong. >> Writers already need to insert into every index, so that's not a >> problem. > > What about HOT? I think that a read would need to lock both the row or tuple (not sure exactly how that would work) and any index used to find the row or tuple (or detect its absence). If a table scan is used, the lock would be at the table level (keeping in mind that this is not a lock which ever blocks anything). An insert or an update which created a new conflicting tuple would hit the table or index lock. A HOT update would hit the row lock. I think.... -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
