Thanks for the PR.

• Errors for EXCLUDE constraints seem okay to add. That is a technical limitation in postgres for this version, which can be removed / reviewed when a future version's release notes mentions otherwise.

• "putting all these in a single issue".

  • +1. Regarding both points above, please avoid unrelated changes in the same PR - for simplicity / comprehension.

Lastly, as of now, SQLancer is adding support for features in v13 - #1072 . Also, there is already a PR for force_parallel_mode which is waiting for v16 support.

LGTM! @robins, do you think this is ready to be merged as well?

The changes are good and the 2 errors seem required too.
The force_parallel_mode is an unnecessary addition here (like the other PR), but otherwise LGTM too.

@yaojiejia - Any chances you're using a non-v13 postgres build to test these?

LGTM! @robins, do you think this is ready to be merged as well?

The changes are good and the 2 errors seem required too. The force_parallel_mode is an unnecessary addition here (like the other PR), but otherwise LGTM too.

@yaojiejia - Any chances you're using a non-v13 postgres build to test these?

Yep I think that is the case, I have been using v17 to test these and every time I get the force parallel mode issues. Just revert my local back to 13, so it should be good now.

Yep I think that is the case, I have been using v17 to test these and every time I get the force parallel mode issues. Just revert my local back to 13, so it should be good now.

I think this is still part of the PR? Anyway, I'm merging this for now to not block progress.