Re:What's new in the Postgres 16 query planner (a.k.a. optim...
by Defman on Friday February 09, 2024 @12:58AM
(#39311854)
You can download the whole visualizer as a simple html file and use it this way. No need to obfuscate or sanitize anything at all.
Re:What's new in the Postgres 16 query planner (a.k.a. optim...
by uudecoded on Friday February 09, 2024 @01:11AM
(#39311925)
Thank you for sharing - I misunderstood - this is a javascript visualizer, and has no additional analytic capability beyond visualization, or did I miss something?
Re:What's new in the Postgres 16 query planner (a.k.a. optim...
by Defman on Friday February 09, 2024 @01:32AM
(#39312052)
Yeah, you’re right. This is the visualizer that’s linked in the parent comment. I just wanted to point out that you can use it locally without sending your explain plan to anyone. Sorry for the confusion, I’ll edit my original comment.
Re:What's new in the Postgres 16 query planner (a.k.a. optim...
by derhuerst on Friday February 09, 2024 @06:38AM
(#39313809)
I do the same, but because it became tedious to insert the query & query plan manually, I wrote pev2-cli [1].
Re:What's new in the Postgres 16 query planner (a.k.a. optim...
by williamdclt on Friday February 09, 2024 @05:00AM
(#39313279)
Whatever the domain, a query isn't necessarily critical or sensitive. It only is if it contains personal information (eg querying by a bank account number or a name), or if the query itself is part of your competitive advantage (unlikely)
Is there an explain plan sanitizer that is helpful for this situation?