TODO about pgcon2023 HOT 3 OPEN

Some output fields will be missing in the pgcon2023 model:
* There are no existing indexes, so there is a single "Indexes" field, instead of two fields ("Existing Indexes" and "Possible Indexes"). Should we instead replace "Indexes" by "Possible Indexes" and have an empty "Existing Indexes" field? This would harmonize both outputs, but would not be as elegant for the pgcon2023 model.

I think we eventually want support for existing indexes in this model (even if we don't have support for consequences), so that they can be assumed to exist during the selection process (and we don't suggest indexes that already exist). Therefore I'd keep the structure similar to the fully-fledged model in this regard.

from pgcon2023.

Some output fields will be missing in the pgcon2023 model:

• Scans have no impact.
• There are no existing indexes, so there is a single "Indexes" field, instead of two fields ("Existing Indexes" and "Possible Indexes"). Should we instead replace "Indexes" by "Possible Indexes" and have an empty "Existing Indexes" field? This would harmonize both outputs, but would not be as elegant for the pgcon2023 model. There are now existing and possible indexes, but the list of existing indexes is fixed (always selected in the solution).
• Some fields will be missing from "Statistics" since there is no consequence, impact, etc (but the remaining fields are the same).

from pgcon2023.

The final solver status (and the amount of time required to solve the problem) will not be reported in the output of this model, as it is not reported in the fully-fledged model.

from pgcon2023.