Graham Gnall

@chaas @mjibson should we include this in #15811 ?

Seeing some variations on repeated queries with select count (*) from mz_site_events limit 1; count ------- 238 (1 row) Time: 3219.900 ms (00:03.220) materialize=> select count (*) from mz_site_events limit...

@jkosh44 that was a materialized view. I've tested again with `serializable` on both a table: ``` materialize=> select count(*) from stuff; count ------- 2 (1 row) Time: 156.434 ms materialize=>...

@chaas @mjibson still relevant?

Porting remaining nice to have issue https://github.com/MaterializeInc/materialize/issues/17148 and some details to our follow up epic -> https://github.com/MaterializeInc/materialize/issues/17130.

Blocked by: #20660

I see! Why is this? Not following. > We'd have to skip through a lot of one-off queries, which are irrelevant for this issue Not that I'm aware of. There...

Agree on focusing scope! One-off selects are still a problem for development workflows and ad hoc analysis, but I think this is the right prioritization given that static dataflows would...