-
Notifications
You must be signed in to change notification settings - Fork 162
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
- Status: Open.#1708 In readysettech/readyset;
- Status: Open.#1706 In readysettech/readyset;
- Status: Open.#1705 In readysettech/readyset;
MySQL: any unrecognized command byte destroys the whole connection instead of returning a clean error
bugSomething isn't workingSomething isn't workingStatus: Open.#1704 In readysettech/readyset;MySQL: warning count is always reported as zero
bugSomething isn't workingSomething isn't workingStatus: Open.#1703 In readysettech/readyset;Postgres: BackendKeyData is never sent -- pg_get_pid() returns 0
bugSomething isn't workingSomething isn't workingStatus: Open.#1702 In readysettech/readyset;Postgres: the COPY protocol is entirely unsupported
bugSomething isn't workingSomething isn't workingStatus: Open.#1701 In readysettech/readyset;Postgres: large object functions destroy the connection
bugSomething isn't workingSomething isn't workingStatus: Open.#1700 In readysettech/readyset;Postgres: LISTEN/NOTIFY appears to succeed but notifications are never delivered
bugSomething isn't workingSomething isn't workingStatus: Open.#1699 In readysettech/readyset;Postgres: NOTICE messages from upstream are never relayed to the client
bugSomething isn't workingSomething isn't workingStatus: Open.#1698 In readysettech/readyset;- Status: Open.#1697 In readysettech/readyset;
ReadySet drops the client connection when a MySQL 8.x client negotiates a collation the upstream lacks (utf8mb4_0900_ai_ci against MySQL 5.7); the same client connected directly to MySQL works
bugSomething isn't workingSomething isn't workingFeature RequestNew feature or requestNew feature or requestStatus: Open.#1695 In readysettech/readyset;