CHECK index unique throw exception

[my-ship-it]

Root Cause Analysis

DirtySnapshot is created on stack, but will be recorded in Resowner.
If transaction abort, there is no chance to remove snapshot from resource owner anyway, which caused invalid memory access.

The stack trace:

_bt_check_unique(DirtySnapshot is created here)
   -> table_index_fetch_tuple_check
      -> ...
         -> AppendOnlyVisimapStore_Init
            -> RegisterSnapshot(snapshot)

UnregisterSnapshot is called in AppendOnlyVisimapStore_Finish. If transaction aborts, there is no chance to call AppendOnlyVisimapStore_Finish.

Reproduce steps

[kd97]

set default_table_access_method=ao_column;
create table test_range_excl(
  id int4,
  room int4range,
  speaker int4range,
  during tsrange,
  exclude using gist (room with =, during with &&),
  exclude using gist (speaker with =, during with &&)
) DISTRIBUTED REPLICATED;
insert into test_range_excl values(1, int4range(123, 123, '[]'), int4range(3, 3, '[]'), '[2010-01-02 10:00, 2010-01-02 11:00)');
// conflicting key value violates exclusion constraint
// expected catch error,but will crash occasionally in aarch64 centos platform
insert into test_range_excl values(1, int4range(123, 123, '[]'), int4range(3, 3, '[]'), '[2010-01-02 10:00, 2010-01-02 11:00)');