You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PG18 introduced a new constraint which is created for all non-null
attributes including p_keys. So now, an attribute which is a p_key will
create two constraints - p_key and not-null constraint.
When adding these constraints on the catalog in ENR, the condition tf2.oid > tf1.oid
will keep the catalog list sorted, however, while removing or updating
any tuple in this catalog list, we compare oids in a way which is
interpreted as remove/update oid of tuple which has an oid greater than
or equal to the requested oid. This leads to catalog corruption since we
are removing/updating a different tuple than the requested one.
This change rectifies this condition and breaks it down based on the
operation being performed.
Task: BABEL-6211
Signed-off-by: Ayush Shah <ayushdsh@amazon.com>
0 commit comments