Joe, a Postgres query optimization bot
postgres.ai
Joe, a Postgres query optimization bot
1–10 of 40 posts
Re: Joe, a Postgres query optimization bot
#2I've just tried the live demo in the Database Lab Community Slack. It looks amazing! Keep it up!
Re: Joe, a Postgres query optimization bot
#3So... this thing gives full read/write/ddl access to production data ...via Slack?
That is a security nightmare. Hard pass.
Re: Joe, a Postgres query optimization bot
#4So... this thing gives full read/write/ddl access to production data ...via Slack? That is a security nightmare. Hard pass.
> Every time when an engineer starts communicating with Joe, a new full-size copy of the database is provisioned.
It looks like users get their own disposable copy. Nothing's run on the prod copy.
Re: Joe, a Postgres query optimization bot
#5So... this thing gives full read/write/ddl access to production data ...via Slack? That is a security nightmare. Hard pass.
> Every time when an engineer starts communicating with Joe, a new full-size copy of the database is provisioned. It looks like users get their own disposable copy. Nothing's run on the prod copy.
Doesn’t change the fact it’s gonna put production data into Slack. Say goodbye to Access Control, and hello to a GDPR/security nightmare.
Re: Joe, a Postgres query optimization bot
#6So... this thing gives full read/write/ddl access to production data ...via Slack? That is a security nightmare. Hard pass.
Yeah, seriously. I wonder how they thought slack and chat interface would be a better than a CLI app...
Re: Joe, a Postgres query optimization bot
#7So... this thing gives full read/write/ddl access to production data ...via Slack? That is a security nightmare. Hard pass.
Yeah, seriously. I wonder how they thought slack and chat interface would be a better than a CLI app...
If you are using a PG client already you are probably not the target audience.
It's easier to tell someone to copy paste a query into Slack to get their weekly insights than teaching them how to set up pgcli or some other gui app. You'd also have to create tightly scoped permissions for everyone who only needs it from time to time.
I'd probably set up something like https://github.com/getredash/redash for these cases though, it's also very user friendly.
Re: Joe, a Postgres query optimization bot
#8So... this thing gives full read/write/ddl access to production data ...via Slack? That is a security nightmare. Hard pass.
Hi, Postgres.ai founder here.
Production is not affected, the chatbot works with thin clones provided by Database Lab https://gitlab.com/postgres-ai/database-lab/.
In general, you are right. If, in your case, using the "raw" databases is unacceptable, it is better to anonymize data first (of course, the physical layout will change in this case).
However, Joe doesn't reveal the data. Engineers see only EXPLAIN (ANALYZE, BUFFERS) plans.
It may be considered acceptable. Of course, there are ways to retrieve particular values with some tricks like "explain analyze ... limit (select value from...)"), but this will be noticeable. Massive data leaks are not possible, Joe filters the output, presenting only metadata -- the whole idea was to provide the data for backend engineers, many of those don't have access to production data.
The question you're raising is broader: let's think how many times we send some personal data to our colleagues in Slack, how is it controlled now? are we okay with that? Emails, tokens, and so on.
At the same time, Joe does boost the development speed because it becomes easier to troubleshoot SQL performance and discuss it with colleagues, collecting reliable facts.
What would you say if it would be: 1. A chatbot for on-prem Mattermost? 2. A specialized GUI, SaaS or standalone?
Re: Joe, a Postgres query optimization bot
#9So... this thing gives full read/write/ddl access to production data ...via Slack? That is a security nightmare. Hard pass.
It's for SQL query optimization, so you probably wouldn't run it on prod.
Re: Joe, a Postgres query optimization bot
#10Earlier quoted context omitted.
Yeah, seriously. I wonder how they thought slack and chat interface would be a better than a CLI app...
If you are using a PG client already you are probably not the target audience. It's easier to tell someone to copy paste a query into Slack to get their weekly insights than teaching them how to set up pgcli or some other gui app. You'd also have to create tightly scoped permissions for everyone who only needs it from time to time. I'd probably set up something like https://github.com/getredash/redash for these cases…
It's for SQL query optimization, not OLAP or similar, so it seems to me like the target audience probably already knows about the psql cli.