Thank you for very detailed feedback!! > People's existing tendency to expose critical data via Slack shouldn't be reinforced I agree with you. However, depen

Thank you for very detailed feedback!! > People's existing tendency to expose critical data via Slack shouldn't be reinforced I agree with you. However, depending on company's policy, raw SQL, even with some concrete values, and EXPLAIN ANALYZE plans may be considered as acceptable for using them in Slack. If it is considered harmful, we have a way to inject anonymization step into the snapshot preparation tool -- see https://gitlab.com/postgres-ai/database-lab/-/blob/master/scripts/create_zfs_snapshot.sh#L173 https://gitlab.com/postgres-ai/database-lab/-/blob/master/sc... (we're thinking how to improve usability here, not losing flexibility). For example, you can run PostgreSQL Anonymizer (https://gitlab.com/dalibo/postgresql_anonymizer https://gitlab.com/dalibo/postgresql_anonymizer). Of course, the physical layout will change, so troubleshooting of, say, VACUUM commands would be affected. But rows cardinality, normally, won't change, so for large enough tables, it totally makes sense do go this route, for SQL troubleshooting&optimization tasks. > Great! Now make that troubleshooting accessible via an authenticated URL and I'm in. We are thinking about the GUI version actively, so stay tuned. And on CLI version as well, but CLI will work in psql (which I'm personally a big fan of, spent 15 years there or so). This means that all the data will be present. In the case of GUI, of course, we are able to work on meta-level, similarly to the Slack version. > If I were to use this tool, I would envision the ideal version of it being self-hosted and able to function independent from any other service. I hear you well, and it generally aligns with our team's vision. Thank you again for awesome feedback! > As for "improv[ing] the level of collaboration of developers and DBAs", great that you're thinking about that, but that's my problem to solve, not Joe's. And depending on my team's existing solutions, this may even rule out Joe simply due to our current tool set. Could you provide some examples of such solutions?