Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

unknown function name: set_config(STRING,STRING,BOOLEAN) when using parameters in `CONCAT` function

Open
#1,207 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
postgresql, python
Domain
databases

Research direction

Start by reproducing the parameterized CONCAT query with asyncpg 0.30.0 against QuestDB 8.1.4 under asyncio and uvloop, then compare it with the reported libpqxx behavior. Done means identifying whether the set_config error comes from asyncpg's query handling or QuestDB compatibility and documenting a confirmed fix or limitation.

Written by the indexing model from the issue text.

Description

  • asyncpg version: 0.30.0
  • PostgreSQL version: QuestDB 8.1.4
  • Do you use a PostgreSQL SaaS? If so, which? Can you reproduce
    the issue with a local PostgreSQL install?
    : -
  • Python version: 3.12.7
  • Platform: Linux 6.11.5-arch1-1
  • Do you use pgbouncer?: no
  • Did you install asyncpg with pip?: yes
  • If you built asyncpg locally, which version of Cython did you use?: -
  • Can the issue be reproduced under both asyncio and
    uvloop?
    : yes

Hello,

I am using asyncpg with QuestDB and I am getting an error with this query:

SELECT FIRST("value")
FROM "values"
WHERE "type" = CONCAT('X', $1, '-', $2)

The error:

asyncpg.exceptions._base.UnknownPostgresError: unknown function name: set_config(STRING,STRING,BOOLEAN)

It works when sending the same query using libpqxx in C++, so I think this is not a problem with QuestDB.

Dominant language
Python
Stars
8.1k
Forks
469
Avg merge
2d 20h
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MagicStack/asyncpg

All issues in MagicStack/asyncpg

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.