> Running arbitrary queries on your customer's database primary is simply never safe, nor can it be made safe Look, the only thing that's never safe is speakin

> Running arbitrary queries on your customer's database primary is simply never safe, nor can it be made safe Look, the only thing that's never safe is speaking in absolutes. > It's not a question of the DB running a little hot. It's accidentally triggering one or more full table scans on a table with millions of records. Does the table have a million records? And I mean come on, a million records and a FTS once a day on modern machine - for the sake of inserts I actually would go with it... Besides may I remind you: materialised views. > It does! Your customer (hopefully) knows their own DB. You don't. Have your customer build the API and they'll support your integration. I envy you. You live in a fantasy land where your customers don't make mistakes and are full pros. I mean that, or you don't care...