4 Commits (a5bef054037a7bd116fd11fa9396c428b4dc5cdd)

Author	SHA1	Message	Date
Jeffrey Walter	80ae7d8e27	#243: Rename pgtde_is_encrypted() to pg_tde_is_encrypted() (#242) ... * Fix is_encrypted function name prefix * main Rename file * Increase dashed line length to match psql output	1 year ago
Zsolt Parragi	8a2b8ec3e5	Access method renaming and conditions (#231) ... * Renamed pg_tde -> pg_tde_basic * The "fork" extension is only visible when it's actally built * Update sysbench tests to use pg_tde_basic	1 year ago
Zsolt Parragi	2a4f0d876d	Renamed master key to principal key (#228) ... This commit contains lots of changes, but it's just a repeated execution of find <...> -exec sed <...>, so everything should work as before.	1 year ago
Muhammad Usama	fefe7b7dea	TDE TupleTableSlot for storing decrypted tuple along with the buffer … (#197) ... * TDE TupleTableSlot for storing decrypted tuple along with the buffer tuple Tuple data in the shared buffer is encrypted. To store the tuple in the tupleTableslot, the tuple data is decrypted into allocated memory. This memory needs to be properly cleaned up. However, with the existing BufferHeapTupleTableSlot, there is no way to free this memory until the end of the current query executor cycle. To address this, the commit introduces TDEBufferHeapTupleTableSlot, a clone of BufferHeapTupleTableSlot that keeps a reference to the allocated decrypted tuple and frees it when the tuple slot is cleared. Most of the code is borrowed from the BufferHeapTupleTableSlot implementation, ensuring that TDEBufferHeapTupleTableSlot can be cast to BufferHeapTupleTableSlot Apart from the above, a workaround to clear the decrypted tuple pointer is added to the TDEBufferHeapTupleTableSlot for cases when the slot is reused while the previously decrypted tuple was cleared out by MemoryContext deletion, instead of through the slot cleanup callback.	1 year ago