Lol yeah.. Anyway in any serious application queries fly past like crazy, create temporary tables, pull the columns from several, and do stuff that's hard to interpret on the fly. Especially a software you just use, didn't write.

Turning on logging is likely more useful. Have done that to understand inner workings of some financial apps.

Or log_statement = 'all' in Postgres.

You don't need to access (or even have access to) the DB server itself (e.g. to read the query-log), you can do everything by just setting a different host to connect to.

yes, this was my first question.

why would i inspect this data, because maybe trying to find a cause to a problem.. are there any other reasons