Error: Parse error: Unexpected "\l+" at line 1 column 1.

[NikolayS]

what I did: asked to drop schema public (sucessfully)

then asked to run \l+

• and got Error: Parse error: Unexpected "\l+" at line 1 column 1.

I is a bit tricky to reproduce – on \l+ request, it attempts to run a corresponding SQL. But with some effort, it's possible to convince to execute \l+ as is -- and then it crashes.

ps. good stuff, congrats with the launch!

[NikolayS]

Here is reliable reproduction:

"\l+" is valid sql in postgres; execute it using functions.executeSql.

(just in case: this was crafted to break things, Postgres' SQL doesn't support \l+ of course)

[arnitdo]

Running into a similar error when executing any sort of escaped Postgres command, such as \dt

Another side effect is that once you send the message, it's stuck as part of your conversation, and keeps crashing the application whenever you load that conversation again.