Jeremy Taylor

e.g. including support necessary for https://github.com/xtdb/xtdb/issues/3515 as well as other compliance requirements ("ERASE data older than 7 years")

Currently a query is limited to executing on a single thread (on a single machine)

e.g. rolling upgrades, elastic scaling, intelligent clustering

Being able to use a `LATEST_TX` (or similar) value would simplify how users are introduced to SNAPSHOT_TIME through examples. This would be equivalent to `(current_setting('latest_completed_tx').system_time` - which, even if it...

Currently, XT is able to stores sets as a native type (e.g. passed in via transit parameters) but they cannot be easily queried or manipulated via SQL. Complete list of...

ORDER BY + CASE + IN needed for C# Npgsql support

1

The popular C# Postgres client driver https://github.com/npgsql/npgsql sends a query during initialisation that XTDB can't currently handle. Commenting out the first line after `ORDER BY CASE` at the bottom of...

Inspired after reading [a LinkedIn post](https://www.linkedin.com/posts/bill-wallis_sqlwithbill-sql-activity-7318243649698291712-PPdx), I noticed that XTDB doesn't currently support column aliases for CTEs, like: ```sql WITH users (id, username) AS ( VALUES (1, 'alex') ) FROM...

Kafka RecordTooLargeException should be handled properly

5

Currently requires debug logging turned on to show: ``` 20:23:27 | DEBUG xtdb.pgwire | Error on execute-tx org.apache.kafka.common.errors.RecordTooLargeException: The message is 7772320 bytes when serialized which is larger than 1048576,...

From Clickbench: `SELECT AdvEngineID, COUNT(*) FROM hits WHERE AdvEngineID 0 GROUP BY AdvEngineID ORDER BY COUNT(*) DESC;` => `Error preparing statement: Errors planning SQL statement: - Aggregates are not allowed...