Public bug reported: If a named query has positional parameters (with $1, $2, and so on), attempting to use it just gives the error message “there is no parameter $1”, the same as if no argument had been provided for that query.
Documentation of how the feature is supposed to work: https://www.pgcli.com/named_queries.md Example: postgres> \ns i SELECT $1 Saved. Time: 0.003s postgres> \n i 42 there is no parameter $1 LINE 1: SELECT $1 It does work using %s instead of $1, but that isn't documented, and doesn't allow for re-ordering parameters or using one multiple times. This broke on upgrading Ubuntu to 20.04 LTS (from 16.04), which has pgcli version 2.2.0. Existing named queries that I had saved in my config and which had previously worked started giving the above error message. ** Affects: pgcli (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876235 Title: "there is no parameter $1" for named queries with numeric parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pgcli/+bug/1876235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs