heap-only tuples, and constraints - Mailing list pgsql-general

From maxxedit@gmail.com
Subject heap-only tuples, and constraints
Date
Msg-id AANLkTi=z1TR9ht6Z_sZevjifVShyA5QTrW7_aW_KSNty@mail.gmail.com
Whole thread Raw
Responses Re: heap-only tuples, and constraints
List pgsql-general
Hi,

Question about heap-only tuples, and constraint checking.

Does this statement (UPDATE user SET email='newChangedVal',
password='existingVal') requires updating an index on user.password?
Or more generally, if an UPDATE includes an explicit but unchanged
value for an index column, does postgres need to also update the index
entries? Or does HOT apply only when indexed column is missing or not
explicit (i.e. password=password)?

Along the same line of thought as above, if password is a foreign key
column and if an UPDATE includes an explicit but unchanged value for
this fk column, does postgres need to check constraint satisfiability?

Thanks

pgsql-general by date:

Previous
From: Chris Berry
Date:
Subject: Delete Trigger
Next
From: Tom Lane
Date:
Subject: Re: Delete Trigger