[axeluhlig]

Problem

Users can provide query plans and the corresponding SQL using the file and sql_file parameters. For very large query plans the URLs are exceeding 1 MB in size, which is causing issues in some of our tooling.

Solution

We add support for providing fileand sql_file as data:application/gzip;base64,.... By compressing the data we significantly reduce the URL size. Decompression is happening locally using DecompressionStream, which all modern browsers support.

Notes

• Providing uncompressed data is still possible
• To protect the host from the browser exhausting local memory we limit the decompressed output size to 1 GB
• I moved the shared URL reader into a new file, so I can test it more easily.