My client is using SET statements, and so my application is pointing to the non-pooled compute URL t
My client is using SET statements, and so my application is pointing to the non-pooled compute URL to avoid the relation not found errors. However i am still seeing the relation not found errors in my client side. This works fine on my local postgres though. Any pointers how i can debug this please ?
