> I agree. But I am thinking about making a database role for each user. The user becomes that role after signing into the front end, like Apache.
I figured. If you isolate the data well enough, it could work. I'm always paranoid when it comes to DB.
> Isn't there the explain command and the \timing option for the command-line client, psql?
Yes, there is. This however doesn't help you with triggers and UDF, which is how you usually create the logic in the DB.
I agree. But I am thinking about making a database role for each user. The user becomes that role after signing into the front end, like Apache.
Apache 2.4's form-based authentication makes this attractive.> The biggest downside is that there are no tools to help to debug or measure the performance of the code you wrote.
Isn't there the explain command (https://www.postgresql.org/docs/current/static/using-explain...) and the \timing option for the command-line client, psql (https://www.postgresql.org/docs/10/static/app-psql.html)?