1 Commits (30cb32b5efe2321001a393d32c04d05e528ccc39)

Author	SHA1	Message	Date
Artem Gavrilov	3e4c889823	PG-1056 xmin and xmax correctness (#292) ... * PG-1056 Add failing test * PG-1056 Use proper AM in test * Fix UPDATE SET ... RETURNING processing for encrypted tuples If `get_heap_tuple` is NULL, the core uses `copy_heap_tuple` instead. The former returns a pointer to a tuple in the slot and the latter makes a copy of such a tuple. For UPDATE SET, the core uses the slot for INSERT and later for RETURNING processing. If we copy the tuple the next happens: 1. The core creates a slot with the generic tuple. 2. It passed to `pg_tdeam_tuple_update()` and it gets a copy of the tuple here [6d4f7e5b7b/src17/access/pg_tdeam_handler.c (L336)]. 3. This generic tuple is filled with the proper data and used for the update here [6d4f7e5b7b/src17/access/pg_tdeam_handler.c (L343)]. 4. Later on, RETURNING processing uses the slot's tuple but is still a generic unmodified one because of the copy. 5. That results in wrong RETURNING data. To avoid this, we should return a pointer to the slot's tuple instead of copying it. Fixes PG-1056 * PG-1056 Split 'update' testcase for tde_heap and tde_heap_basic --------- Co-authored-by: Andrew Pogrebnoy <absourd.noise@gmail.com>	11 months ago
Zsolt Parragi	a683aa3505	PG-979: Run SQL tests with both tde_heap and tde_heap_basic (#291)	12 months ago