Philip Stoev

Blocked by https://github.com/MaterializeInc/materialize/issues/14098

Still failing as before

[gh13879.sql.zip](https://github.com/MaterializeInc/materialize/files/9189918/gh13879.sql.zip) To reproduce, pipe this file through the psql client. It contains a simple schema, a few data rows, one `CREATE MATERIALIZED VIEW` statement and then 20 `CREATE DEFAULT INDEX...

The CPU usage is only reproducible with a Debug build. Under release, CPU usage is negligible and storage and malloc related futures do not stand out. The fact that blobs...

An expanded section of the `perf` report above shows that it ultimately ends up in `malloc`: ``` 16.05% 0.00% timely:work-0 computed [.] ::poll ◆ - ::poll ▒ - 16.03% ::poll...

CPU usage is indeed limited to Debug, so I guess nothing can be done here. The proliferation of blob files no longer occurs.

If we are no longer using mzbuild with Postgres we should also remove `misc/images/psql` to avoid any confusion.

`ENVELOPE UPSERT` is now present in both Zippy and Platform Checks, so this is good to go.

Also seen with `CREATE INDEX` and the test case for gh 13879 , if one requires a reproduction scenario.

`ENVELOPE DEBEZIUM UPSERT` is now present in both Zippy and Platform Checks, so this is good to go.