`PostgreSQL` differential fuzzing

Hi,

With differential fuzzing of sqlparser vs postgres 18, I have collected a very large list of missing features, mistakenly rejected statements, and generally speaking, bugs. I want to do the same for SQLite, since these two are the dialects I use primarily in my projects.

This list is currently non-deduplicated (meaning I am not sure exactly which statements are redounded) and is currently at about 10k minimized entries (minimized according to honggfuzz).

I made several PRs over the weekend trying to address the most common cases the fuzzer was finding, but it is way too much work to do on my own. Also, I do not think that just opening 10k issues or a single issue with 10k errors in it is viable.

How do you suggest I proceed?

Best,
Luca

The report describes roughly 10,000 minimized PostgreSQL differential-fuzzing entries but names no source files, tests, or entry points. Start by reviewing the fuzzing results and obtaining a maintainer-approved way to deduplicate and scope them; done would require an agreed process and individually actionable fixes.

Written by the indexing model from the issue text.