`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

Il report descrive circa 10.000 voci minimizzate di differential-fuzzing di PostgreSQL, ma non indica alcun file sorgente, test o punto di ingresso. Inizia esaminando i risultati del fuzzing e ottenendo un metodo approvato da un maintainer per deduplicarli e definirne l'ambito; il lavoro sarebbe considerato completato quando fossero disponibili un processo concordato e correzioni attuabili individualmente.

Scritto dal modello di indicizzazione a partire dal testo della issue.