Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vNEen-00ElPs-0I for pgsql-odbc@arkaria.postgresql.org; Sun, 23 Nov 2025 18:17:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vNEel-00F9gs-2N for pgsql-odbc@arkaria.postgresql.org; Sun, 23 Nov 2025 18:17:52 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vNEel-00F9e1-10 for pgsql-odbc@lists.postgresql.org; Sun, 23 Nov 2025 18:17:51 +0000 Received: from mail-yx1-xb136.google.com ([2607:f8b0:4864:20::b136]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vNEei-0014qq-34 for pgsql-odbc@postgresql.org; Sun, 23 Nov 2025 18:17:50 +0000 Received: by mail-yx1-xb136.google.com with SMTP id 956f58d0204a3-63fc72db706so2936593d50.2 for ; Sun, 23 Nov 2025 10:17:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1763921867; x=1764526667; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=Ve0qf2v3kDR+JYrt89EItvYvo6+cN7WdAe2pNs4hHgw=; b=XU2m4qqYw3TWolnYtS1EgFcDdk5uMKPzi3oFV7+JDIO2F8aGyVlynaJ7+uk3pRmVW0 HMfZLyQYcD2OhnuGhUuiZOkaFGu+Xvy5qRQkQlzYVRUPz8JHblS9XrVX+ekw51DHCNZ2 hjow/93ktwlHhLHkzrixHXD4CUth4dPX7Xpn3MOYnTYaVZsWcLAXguTD7iMGVANIZop/ qCUlfJPvA0SVQvNV3hbOo7QDaAZdQW64GEacQxJ+4/IdUUJDaZGwT3l3Zll0JGfcTecn 5o8wDeqYO2gf6PD6PFQ4aBKMj9tLp72XvvlcsGcxMc23qKcN4+M4qHgR4ozSVyDjD2G2 aDqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763921867; x=1764526667; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Ve0qf2v3kDR+JYrt89EItvYvo6+cN7WdAe2pNs4hHgw=; b=tc21ka1SeUp2F5Zt48UmJ+DcxTVGyK9u1FTsksbriWWPTsLivZ/0nUSIfMu/vFnqGe 6Y++REPdYPdaZQ7zrIWXp+YQXf3Q94I6LqFhhSZ3Qta4dwT95zURNaYq1E5KZKDN46zK 13wgi3YkLsopWlwWaGlXrkL6mw+V5U73SdNK551iI1zkzZGW4i4IgnkjSstGF1ObBuxi szSavJ4OZOGiEczHHb91XHsr+glbZGg3Ot/DrRZ6zUkS/9WwijGDUCQQoBekL/TLfIqh tdVXTCiTGkC7VOp43PCKn8qFE5P7zvB78lQcrzPIkWD/F4Y4f1gS8l41zj93tLJxy9rg xvTw== X-Gm-Message-State: AOJu0YyIKVSySH9/UEkSKrlaBFP5x3gYbSxANNiSoJVRyrvzlxynQK8k KzgYQFFs8RwDPTnSRt7lVT2ZuM7KpuXk8/rq0lPlR3Ia8NzDaxh8iAGeN/3Hxs6K19YMAWfci6b WmgGHxOiUt+dtr/xHFlriyTatgJUglCCUYU8z X-Gm-Gg: ASbGncuIHj9+pSOsZ1RhSTdoaapUiqxxBxiDXKn8CsxEEFsF3zB4Ufm+gzWIbIkrico wPZQyK5HRmbV8R8cnow0H83vEnBNnsdxhWHiAlhHKjxpE1HpVTx2J9NzvXayzXqaFlPNeU9xXzU OZqEEN5GDOqEKEr/38jnKElYgHAtmVsjgpo9uvQYaDqYK/L9Qi96a2W/72+ic9+V6sO09mPRqGG glcn/DNeMInmmmdyK12I9DD/sqyJrQFtcIMl3udKa1t0n1ytkK0o29VJ3zZMkjTIOnL/KhVxyDT Xn+Juyoh23nD6RxcjPcvP1551LxCyxHGiTDEspA= X-Google-Smtp-Source: AGHT+IHmaivvRL/Q2tL8kHqUM0LqL3z4TKz2e3I2l8bBkeKKbEFZ0zrhuGQejH2laZPh5ffWaww5giFaQotFuWDJpHc= X-Received: by 2002:a05:690e:d4f:b0:63f:b017:f662 with SMTP id 956f58d0204a3-64302a90a4cmr6976586d50.10.1763921867401; Sun, 23 Nov 2025 10:17:47 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Igor Korot Date: Sun, 23 Nov 2025 10:17:36 -0800 X-Gm-Features: AWmQ_bnN1lnTzbjXHhtvvA7P3OwaOPpnNNU0M2iJznmQUwWHuh9Pq5g2hBbek7I Message-ID: Subject: Fwd: ODBC fails to recognize event trigger removal To: PostgreSQL ODBC list Content-Type: multipart/alternative; boundary="000000000000516e61064447104a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000516e61064447104a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Originally sent to PostgreSQL general ML. Thank you. ---------- Forwarded message --------- From: Igor Korot Date: Sun, Nov 23, 2025 at 4:44=E2=80=AFAM Subject: ODBC fails to recognize event trigger removal To: pgsql-generallists.postgresql.org Hi, ALL, [code] postgres=3D# CREATE OR REPLACE FUNCTION __watch_schema_changes() RETURNS event_trigger LANGUAGE plpgsql AS $$ BEGIN NOTIFY tg_tag; END; $$; CREATE FUNCTION postgres=3D# CREATE EVENT TRIGGER schema_change_notify ON ddl_command_end WHEN TAG IN('CREATE TABLE', 'ALTER TABLE', 'DROP TABLE', 'CREATE INDEX', 'DROP INDEX') EXECUTE PROCEDURE __watch_schema_changes(); CREATE EVENT TRIGGER postgres=3D# DROP EVENT TRIGGER schema_change_notify CASCADE; DROP EVENT TRIGGER postgres=3D# \q igor@WaylandGnome ~/unixODBC-2.3.12 $ isql postgres postgres wasqra123 +---------------------------------------+ | Connected! | | | | sql-statement | | help [tablename] | | echo [string] | | quit | | | +---------------------------------------+ SQL> CREATE OR REPLACE FUNCTION __watch_schema_changes() RETURNS event_trigger LANGUAGE plpgsql AS $$ BEGIN NOTIFY tg_tag; END; $$; SQLRowCount returns -1 SQL> CREATE EVENT TRIGGER schema_change_notify ON ddl_command_end WHEN TAG IN('CREATE TABLE', 'ALTER TABLE', 'DROP TABLE', 'CREATE INDEX', 'DROP INDEX') EXECUTE PROCEDURE __watch_schema_changes(); [ISQL]ERROR: Could not SQLExecute SQL> quit igor@WaylandGnome ~/unixODBC-2.3.12 $ [/code] Server version 16.2 Driver version 11.1 Anybody aware of this? Thank you. --000000000000516e61064447104a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Originally sent to PostgreSQL general ML.

Thank you.
---------- Forwarded message ---------
From: <= strong class=3D"gmail_sendername" dir=3D"auto">Igor Korot <ikorot01@gmail.com= >
Date: Sun, Nov 23, 2025 at 4:44=E2=80=AFAM
Subject: ODBC = fails to recognize event trigger removal
To: pgsql-generallists.postgresql.org <pgsql-general@lists.postgres= ql.org>


Hi, ALL,

[code]
postgres=3D# CREATE OR REPLACE FUNCTION __watch_schema_changes() RETURNS event_trigger LANGUAGE plpgsql AS $$ BEGIN NOTIFY tg_tag; END; $$;
CREATE FUNCTION
postgres=3D# CREATE EVENT TRIGGER schema_change_notify ON
ddl_command_end WHEN TAG IN('CREATE TABLE', 'ALTER TABLE', = 'DROP
TABLE', 'CREATE INDEX', 'DROP INDEX') EXECUTE PROCEDURE=
__watch_schema_changes();
CREATE EVENT TRIGGER
postgres=3D# DROP EVENT TRIGGER schema_change_notify CASCADE;
DROP EVENT TRIGGER
postgres=3D# \q
igor@WaylandGnome ~/unixODBC-2.3.12 $ isql postgres postgres wasqra123
+---------------------------------------+
| Connected!=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |
|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|
| sql-statement=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|
| help [tablename]=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 |
| echo [string]=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|
| quit=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |
|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|
+---------------------------------------+
SQL> CREATE OR REPLACE FUNCTION __watch_schema_changes() RETURNS
event_trigger LANGUAGE plpgsql AS $$ BEGIN NOTIFY tg_tag; END; $$;
SQLRowCount returns -1
SQL> CREATE EVENT TRIGGER schema_change_notify ON ddl_command_end WHEN TAG IN('CREATE TABLE', 'ALTER TABLE', 'DROP TABLE',= 'CREATE INDEX',
'DROP INDEX') EXECUTE PROCEDURE __watch_schema_changes();
[ISQL]ERROR: Could not SQLExecute
SQL> quit
igor@WaylandGnome ~/unixODBC-2.3.12 $
[/code]

Server version 16.2
Driver version 11.1

Anybody aware of this?

Thank you.
--000000000000516e61064447104a--