This is a scenario where the Postgres
This is a scenario where the Postgres syntax is a bit unfortunate. SET in the context of UPDATE commands (keyword) and SET in the context of session state management (statement) are entirely unrelated, from the message protocol all the way down to the internals and back. They just happen to share the same name.
SET ROLE and such that are for session state management are going to be a problem, almost regardless of how you wrap them. We've done work to make the system more resilient, so you might get lucky, but generally I'd avoid those. The SET keyword in the context of UPDATE statements is fine, go nuts with it.
SET ROLE and such that are for session state management are going to be a problem, almost regardless of how you wrap them. We've done work to make the system more resilient, so you might get lucky, but generally I'd avoid those. The SET keyword in the context of UPDATE statements is fine, go nuts with it.
2 Replies
Unknown User•2mo ago
Message Not Public
Sign In & Join Server To View
Yeah. I think that's the best possible approach in our scenario.
If you're up for it, let me know how it works for you. If you run into any particular blockers I'd be interested to know.