umanwizard

This language is similarly confusing: > For example, Pin, Pin, Pin all guarantee that T won't be moved. And directly contradicts other language in the same paragraph (which is actually...

Yes, but this is about 45000x easier than #14133, and independently useful, so we might want to support it directly rather than waiting for that.

Did we get rid of the `WITH` options in different places, and now we only use the `WITH` keyword on the options that apply to the entire DDL statement?

We aren't clear either, that's the problem. Someone needs to spend a few hours (or longer if necessary) thinking hard about this and either write a formal justification for the...

IIRC there are also possible states where we hang indefinitely rather than crash looping. I'll describe one here if I can remember or find it.

I don't think this can be closed yet. It is conceptually distinct from issues of the form "TCP connections can randomly go down". Even if we consider such issues to...

Initially the processes have no state, and thus it does not make sense to distinguish between various incarnations of them. For example, if process 1 is connected to process 2...

All issues that I know about are now fixed. Leaving this open pending QA approval.

The code for this has now landed, with the caveat that errors are un-retractable until https://github.com/MaterializeInc/materialize/issues/14084 lands. Leaving the issue open pending QA signoff as the code is still only...

The code for this has now landed, with the caveat that errors are un-retractable until https://github.com/MaterializeInc/materialize/issues/14084 lands. Leaving the issue open pending QA signoff as the code is still only...