Austin Bonander

For those searching the issue tracker, I'm adding some keywords here: ConnectionAborted, database.windows.net

@DaAitch @liolin would both of you please provide the output of `EXPLAIN (VERBOSE, FORMAT JSON) ` as that is what the Postgres driver uses for nullability analysis.

That's actually not a false positive, look back at the view you created: ```sql CREATE VIEW book AS SELECT m.id as id, m.title as title, b.author as author, m.raiting as...

I'm benchmarking a change that forces the proc macros to compile with optimizations on, when I open the PR I'd like someone to try building with my branch to see...

> Sorry if I am being a bit naive but that would work only if `cargo build --release` worked, no? No, because proc macros and build scripts are _always_ built...

We are working to make the runtime and TLS features orthogonal so you can disable TLS if you don't need it. That work isn't on the `next` branch, it's going...

I don't think we can fix this without analyzing the SQL query ourselves, Postgres just doesn't tell us enough here. All it tells us is that `c2` comes from the...

@mehcode suggests using `explain verbose`, which using JSON format gives us output like this: ``` postgres=# explain (verbose true, format json) select * from null_join_test left join null_join_test njt on...

For the above query: ``` [ { "Plan": { "Node Type": "Merge Join", "Parallel Aware": false, "Join Type": "Right", "Startup Cost": 672.10, "Total Cost": 1136.80, "Plan Rows": 30623, "Plan Width":...

Potential strategy: * Given the outermost plan, use the `Outputs` key to map (potentially aliased) columns to their original names * Perform a depth-first traversal of the plan tree, adding...