Replica Identity tuples are not encrypted in the XLog

[dAdAbird]

DELETE and UPDATE producing records with Replica Identity tuples in the XLog. These tuples/records are not encrypted. We should encrypt them. See ExtractReplicaIdentity() calls and XLog stuff in pg_tde_delete() and pg_tde_update().

[user411]

Would appreciate environment specifics (Umbrel or local dev env) and platform with pictures like this.

That picture looks like an error was involved in communicating with the backend (from the "[object..." in the message), but I see green logo which implies the backend was online.

I have yet to see the overlay issue that this picture seems to show, but that is what Roman was reporting when switching to and from a browser tab with the wallet running in it.

[Christewart]

Would appreciate environment specifics (Umbrel or local dev env) and platform with pictures like this.

This was on umbrel at commit 19b727288be9fa8832fcd301742058b1920e787d

I have yet to see the overlay issue that this picture seems to show, but that is what Roman was reporting when switching to and from a browser tab with the wallet running in it.

I don't believe I did any tab switching. I believe I had just accepted an offer in my inbox, switched to the contracts tab and was waiting for the UI notification to happen to indicate the tx had been broadcast so i could link my counterparty to that tx on mempool.space