Skip to content

Automatic cleanup of transactional variables #50

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
vitalca opened this issue Dec 22, 2022 · 1 comment
Open

Automatic cleanup of transactional variables #50

vitalca opened this issue Dec 22, 2022 · 1 comment

Comments

@vitalca
Copy link

vitalca commented Dec 22, 2022

Hello,

I use the extension in order to set up the current app security context for audit triggers. There is a connection pooler, working in the transaction pooling mode, meaning that the same DB session (including pg vars data) can be shared between different JDBC connections.

I'd like a transactional variable to be automatically cleaned up at the end of each transaction.
Any ideas on how to do this?

@vitalca vitalca changed the title Automatic cleanup of transaction variables Automatic cleanup of transactional variables Dec 22, 2022
@vitalca
Copy link
Author

vitalca commented Dec 23, 2022

I suppose I should stick to the standard functions set_config() / current_setting() rather than using the extension to achieve the desired behavior.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant