postgrespro/jsquery

Installation in a specific schema

Opened this issue · 1 comments

Hello,

This is more a question, rather than an issue.

Why is it important to install jsquery into the schema of use, and not any schema like with other extensions?

Is there some specific reason for this constraint?

Thank you.

Also, dropping this extension does not remove its four operator families (all other objects are correctly dropped). We are talking about pg17.2. (This seems to be an intermittent issue. I have seen it happening in one of the schemas.)

This is rather peculiar behaviour. Is it on purpose?