Description
Summary
In the alter session command should be specified that this command is a wrapper for the postgres set command .
Which , if executed inside a transaction , and the transaction subsequently rolled back , the command will not persist.
This is specified in the [documentation](https://www.postgresql.org/docs/current/sql-set.html) as well.
If SET (or equivalently SET SESSION) is issued within a transaction that is later aborted, the effects of the SET command disappear when the transaction is rolled back. Once the surrounding transaction is committed, the effects will persist until the end of the session, unless overridden by another SET.
Where did you see the problem?
https://techsupport.enterprisedb.com/tickets/48332
Expected behavior
Customer complained that this is not specified in the docs , therefore assuming 100% compatibility.
Which unfortunately depends from the server itself , beyond semantics
link to docs
Prdocs/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_sql
Screenshots
No response
Browser / Platform
No response
Additional notes
No response