Idle in transaction #1038

New issue

Open

opened 2026-03-04 11:36:32 -05:00 by deekerman · 2 comments

deekerman commented

2026-03-04 11:36:32 -05:00

Owner

Originally created by @ttyyzzqq on GitHub (Dec 12, 2025).

Hello, I've encountered the same issue as described in #8303. I don't understand why the PostgreSQL server has uncommitted transactions, which are not visible to users. I would like to know what parameters I can modify to prevent this situation? Thank you.

SELECT c.oid, a.attnum, a.attname, c.relname, n.nspname, a.attnotnull OR (t.typtype = 'd' AND t.typnotnull), a.attidentity != '' OR pg_catalog.pg_get_expr(d.adbin, d.adrelid) LIKE '%nextval(%' FROM pg_catalog.pg_class c JOIN pg_catalog.pg_namespace n ON (c.relnamespace = n.oid) JOIN pg_catalog.pg_attribute a ON (c.oid = a.attrelid) JOIN pg_catalog.pg_type t ON (a.atttypid = t.oid) LEFT JOIN pg_catalog.pg_attrdef d ON (d.adrelid = a.attrelid AND d.adnum = a.attnum) JOIN (SELECT 24028802 AS oid , 1 AS attnum UNION ALL SELECT 24028802, 2 UNION ALL SELECT 24028802, 3 UNION ALL SELECT 24028802, 4 UNION ALL SELECT 24028802, 5 UNION ALL SELECT 24028802, 6 UNION ALL SELECT 24028802, 7 UNION ALL SELECT 24028802, 8 UNION ALL SELECT 24028802, 9 UNION ALL SELECT 24028802, 10 UNION ALL SELECT 24028802, 11 UNION ALL SELECT 24028802, 12 UNION ALL SELECT 24028802, 13 UNION ALL SELECT 24028802, 14 UNION ALL SELECT 24028802, 15 UNION ALL SELECT 24028802, 16 UNION ALL SELECT 24028802, 17 UNION ALL SELECT 24028802, 18 UNION ALL SELECT 24028802, 19 UNION ALL SELECT 24028802, 20 UNION ALL SELECT 24028802, 21 UNION ALL SELECT 24028802, 22 UNION ALL SELECT 24028802, 23 UNION ALL SELECT 24028802, 24 UNION ALL SELECT 24028802, 25 UNION ALL SELECT 24028802, 26 UNION ALL SELECT 24028802, 27 UNION ALL SELECT 24028802, 28 UNION ALL SELECT 24028802, 29 UNION ALL SELECT 24028802, 30 UNION ALL SELECT 24028802, 31 UNION ALL SELECT 24028802, 32 UNION ALL SELECT 24028802, 33 UNION ALL SELECT 24028802, 34 UNION ALL SELECT 24028802, 35 UNION ALL SELECT 24028802, 36) vals ON (c.oid = vals.oid AND a.attnum = vals.attnum)

Originally created by @ttyyzzqq on GitHub (Dec 12, 2025). Hello, I've encountered the same issue as described in [#8303](https://github.com/dbeaver/dbeaver/issues/8303). I don't understand why the PostgreSQL server has uncommitted transactions, which are not visible to users. I would like to know what parameters I can modify to prevent this situation? Thank you. ``` SELECT c.oid, a.attnum, a.attname, c.relname, n.nspname, a.attnotnull OR (t.typtype = 'd' AND t.typnotnull), a.attidentity != '' OR pg_catalog.pg_get_expr(d.adbin, d.adrelid) LIKE '%nextval(%' FROM pg_catalog.pg_class c JOIN pg_catalog.pg_namespace n ON (c.relnamespace = n.oid) JOIN pg_catalog.pg_attribute a ON (c.oid = a.attrelid) JOIN pg_catalog.pg_type t ON (a.atttypid = t.oid) LEFT JOIN pg_catalog.pg_attrdef d ON (d.adrelid = a.attrelid AND d.adnum = a.attnum) JOIN (SELECT 24028802 AS oid , 1 AS attnum UNION ALL SELECT 24028802, 2 UNION ALL SELECT 24028802, 3 UNION ALL SELECT 24028802, 4 UNION ALL SELECT 24028802, 5 UNION ALL SELECT 24028802, 6 UNION ALL SELECT 24028802, 7 UNION ALL SELECT 24028802, 8 UNION ALL SELECT 24028802, 9 UNION ALL SELECT 24028802, 10 UNION ALL SELECT 24028802, 11 UNION ALL SELECT 24028802, 12 UNION ALL SELECT 24028802, 13 UNION ALL SELECT 24028802, 14 UNION ALL SELECT 24028802, 15 UNION ALL SELECT 24028802, 16 UNION ALL SELECT 24028802, 17 UNION ALL SELECT 24028802, 18 UNION ALL SELECT 24028802, 19 UNION ALL SELECT 24028802, 20 UNION ALL SELECT 24028802, 21 UNION ALL SELECT 24028802, 22 UNION ALL SELECT 24028802, 23 UNION ALL SELECT 24028802, 24 UNION ALL SELECT 24028802, 25 UNION ALL SELECT 24028802, 26 UNION ALL SELECT 24028802, 27 UNION ALL SELECT 24028802, 28 UNION ALL SELECT 24028802, 29 UNION ALL SELECT 24028802, 30 UNION ALL SELECT 24028802, 31 UNION ALL SELECT 24028802, 32 UNION ALL SELECT 24028802, 33 UNION ALL SELECT 24028802, 34 UNION ALL SELECT 24028802, 35 UNION ALL SELECT 24028802, 36) vals ON (c.oid = vals.oid AND a.attnum = vals.attnum) ```

deekerman added the

x:postgresql

xf:metadata

wait for response

labels

2026-03-04 11:36:32 -05:00

deekerman commented

2026-03-04 11:36:42 -05:00

Author

Owner

@nickwhitacker99-web commented on GitHub (Dec 12, 2025):

@nickwhitacker99-web commented on GitHub (Dec 12, 2025): [](url)

deekerman commented

2026-03-04 11:36:54 -05:00

Author

Owner

@LonwoLonwo commented on GitHub (Dec 18, 2025):

Hello @ttyyzzqq

This request is a system request sent by the PostgreSQL driver.
Maybe DBeaver/CloudBeaver triggers it by making some metadata requests to your database.
Could you please explain to me - how exactly these transactions bother you?

@LonwoLonwo commented on GitHub (Dec 18, 2025): Hello @ttyyzzqq This request is a system request sent by the PostgreSQL driver. Maybe DBeaver/CloudBeaver triggers it by making some metadata requests to your database. Could you please explain to me - how exactly these transactions bother you?