permission denied on "SET SESSION AUTHORIZATION [username]"

I am utilizing row-level-security policies to create different ‘areas’ depending on which database user is currently connected. On development this has been working fine.

But in production with digital ocean databases I was unable to use the “SET SESSION AUTHORIZATION” command. This command changes which role the connection uses for future requests.

This means I am unable to switch the connection’s role (aka switch which area is accessible) depending on the request’s context.

This was not expected and is causing major issues. I believe that this is a feature that is not supported - but I would like to be thorough. Am I missing something? Is there a way around this? Or will I have to (bleh) manage my own database on a VM or something?

Error message: “PG::InsufficientPrivilege: ERROR: permission denied to set session authorization (ActiveRecord::StatementInvalid)”