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.94.2) (envelope-from ) id 1tfwD7-006LjM-Cd for pgsql-general@arkaria.postgresql.org; Thu, 06 Feb 2025 07:22:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tfwD3-004ymk-R5 for pgsql-general@arkaria.postgresql.org; Thu, 06 Feb 2025 07:22:01 +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.94.2) (envelope-from ) id 1tfwD3-004ymc-G9 for pgsql-general@lists.postgresql.org; Thu, 06 Feb 2025 07:22:01 +0000 Received: from mail-yb1-xb2b.google.com ([2607:f8b0:4864:20::b2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tfwD1-003U3o-06 for pgsql-general@lists.postgresql.org; Thu, 06 Feb 2025 07:22:00 +0000 Received: by mail-yb1-xb2b.google.com with SMTP id 3f1490d57ef6-e573136107bso488202276.3 for ; Wed, 05 Feb 2025 23:21:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738826518; x=1739431318; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=OxhfvpYm41P5EvOWbpgeAPP6CqXvJuIzkWW0SbMmrlo=; b=k4VJmhInW3qxScoJwNale1oENcutc+Lwqil5baGQZg1/3IAuUlE0gDuyqEO5RVGOKp b6AxqXZw58dsTj8aQk6IBNwfQnyduYZNHtZ+iYmDdrqC2FTN85zZt20gWw/Sfwokm3E0 8KmU5HX4SYH1YfNeyLqUgDm0r3UYgZNQDl+zfxXiD1aenYJTZbmPRfIczFh89ezQNm9s riZOl/xVCWxKoqgRIsRzctt0I0yltxCPX/pUTUnpY6iWFIW2JLmeiyPSXg7aZJESg7k/ CGUPS4hv6p+2UoI/Kw+USh8koKYTi/wzVwTVXfeZYEcbHLtVXnJ0IErlpAxJ1AW5DJrW WcXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738826518; x=1739431318; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=OxhfvpYm41P5EvOWbpgeAPP6CqXvJuIzkWW0SbMmrlo=; b=mIGtb06bJE9BUqRnojFTc7Ak0co/NOKnBsp9nJY+7NiHczAjatznqoTdgt3ul3TG6Y AeduqzOlnBPRirxu1F45YdkoIT1CSIuRiEBgQT2RdRpEGCt9KGblKVnD6iBxAfhXmI8/ vxH3C11AxqqSe55StsuapyORjtSBWyDJZWR8F8C45j5a1WwCeo3uvFHFgzr/xOg5fnzx tRVar3BTmH/mrJj7A6R0m9nekhCmH0THZjt8vJAq0VWsoofbIlleoda+dXWsQ8YmzWX1 JvAgusQkB23x1y0ZHs2XA7zj5rBK50O6bfhtDfPRG7HVeAyhoQ2M/iPUQ14/rx90TFXz mF6Q== X-Gm-Message-State: AOJu0Yx7jtu0NGGJqlIYNOcnQi95L/QxFu0FrvXkyipdYSnV9In5A3Ao rsLAheUVPVXgP+enUnBOgkH+l7tsUuMRGYAFZ9+okfkJj6cc5qoIMGIWOJiIfcB3iL8S9bSOUen a9LKr982sH4xu7oedqFA2y+cOHWaidzI0XdA= X-Gm-Gg: ASbGncs9OEGEjtIIvBKgtwC/6MgeI6PUoEYbOpVXsHmFa9Yr0jNozbIBo07W4tu+JDb z2ByvdDN0rt5J9uSdR/EfeMaPLnUQVr5muxdpsmZHFA8p4eFo0+KUq1cpY8XANveKMtSbvv1AGo Yn7FXuXDcFBbEuDMxMEsQYZ4g+FgnEQw== X-Google-Smtp-Source: AGHT+IHRRZVCuFstFQB9hDUZ1LQ1s2Wo5xSyR7Jdl2cYy59zuUyxYBwDFf0RP1mRt7zZdwu1BZNq0Lh1q/k7XjIgKts= X-Received: by 2002:a05:6902:1702:b0:e5b:1fb9:96fe with SMTP id 3f1490d57ef6-e5b25a0f3e5mr4773085276.17.1738826518351; Wed, 05 Feb 2025 23:21:58 -0800 (PST) MIME-Version: 1.0 From: Igor Korot Date: Thu, 6 Feb 2025 01:21:17 -0600 X-Gm-Features: AWEUYZnNvqoCrEd8M8DUpu1Cb70Roj25TPbSduXIRrJ3iS_cYElBDInwPQzB-_s Message-ID: Subject: How to get a notification To: "pgsql-generallists.postgresql.org" Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, ALL, In my code I'm running following: queries.push_back( L"CREATE FUNCTION __watch_schema_changes() RETURNS event_trigger LANGUAGE plpgsql AS $$ BEGIN NOTIFY tg_tag; END; $$;" ); queries.push_back( L"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();" ); My questions are: 1 Is there a better way to get notification about CREATE/ALTER/DROP TABLE? 2. How do I receive notification abut the event with the object name? Thank you.