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 1rySK0-00GMTi-TU for pgsql-general@arkaria.postgresql.org; Sun, 21 Apr 2024 08:13:12 +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 1rySJz-00DacI-GS for pgsql-general@arkaria.postgresql.org; Sun, 21 Apr 2024 08:13:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rySJz-00Dac9-3F for pgsql-general@lists.postgresql.org; Sun, 21 Apr 2024 08:13:11 +0000 Received: from mail-oo1-xc29.google.com ([2607:f8b0:4864:20::c29]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rySJs-0026VQ-GB for pgsql-general@lists.postgresql.org; Sun, 21 Apr 2024 08:13:10 +0000 Received: by mail-oo1-xc29.google.com with SMTP id 006d021491bc7-5af10e553b0so24677eaf.1 for ; Sun, 21 Apr 2024 01:13:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713687182; x=1714291982; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=RTaXkjrvzWsJr8ziW8kbjoDWXYMy7mfsD3F9LISNTPs=; b=m5w9iRxEEIPbZV9QtQ5V+okkst6ZEs1ej0TyMDboJFHht7ilGKLRONGf26594p5vDw B3bdO8VNKz2QWx/DRC1+6J4GimdZnllHwXgbldSDeVKXWEOB+7ktN6Yx6DHVDMEANgz3 1kZIuOyEbN3MoheFrCqcamkcerScByHPaIY8QxQRM/SUKcsSqcIWMdXko8PJ70wacq4D qo2r/pjtcaQnuFe6R1LoXlvj3qOCHLtwBiKEIXB23oqd7GMLTDnsjOJnB9vkqBAnOJ7Y EOXFNPhbOLB6mj7IZmoG8lO0Hebnjxx/eX/O6sF+0mf7v2kl+KtORHG/ARsd1sZ6LP4t W8lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713687182; x=1714291982; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=RTaXkjrvzWsJr8ziW8kbjoDWXYMy7mfsD3F9LISNTPs=; b=ZpFc6mLmv4R4XXCwfptd///OfsUZBpucT4iMdYtl4kgKbiqf7DRd16Ny9zxLa5svm/ OvDfiTywuG+OvYYQxMDWVGQCPl8AXQTGc9mwBSIm/KyIisQNsrf0XLWYbwA+JrCrn5Ok 2StuHJYpQl4v8T/uo2EoNeU4UJCeC25E7351n3nQ6LYuxurXqI+XeR/63NrDzvI7YbW4 bONaHeElm7QwbX1CdifJthn/SBdDXTZAwcychi0XtXYexhvz2TNT6OhQHYVBFNkXF9RK frBEScAIS4kZ0y42XXSc725xIv8yi9LaLVZyUylzDlsDH4zpenJds2nQ1C8zhp6aaAv3 NUkA== X-Gm-Message-State: AOJu0YySvTHOcORs5uC8E+7YlX9+WAP5buhhey74HypY45liJhx5ntKt /NEu9fyxAViaJnNltK65Vrzcdz32TQNUNXLOu5WIg38ro9V8OCEt+tgeDmKdZ/aMajJe/6GrIJg IgEbfhYG77oe4T9Rx9E0DkpbSZsQV1NSdU2E= X-Google-Smtp-Source: AGHT+IGnBtWC7JRf97M1sPOElpYDdWP2LBTGu0oarjHJtUivTeJS1OIW5M6dA0GVqoVkZ+cC5vZTewv2tby69smJ7yA= X-Received: by 2002:a05:6359:4f87:b0:17f:7807:320c with SMTP id nh7-20020a0563594f8700b0017f7807320cmr8801117rwb.5.1713687181690; Sun, 21 Apr 2024 01:13:01 -0700 (PDT) MIME-Version: 1.0 From: yudhi s Date: Sun, 21 Apr 2024 13:42:49 +0530 Message-ID: Subject: error in trigger creation To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000b890cd061696e30d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b890cd061696e30d Content-Type: text/plain; charset="UTF-8" Hi All, We are seeing privilege issues while creating event triggers. It says the user "*must be a superuser to create an event trigger*". So my question is , if we have application user as "app_user" which is responsible for creating database objects in schema "app_schema" and also we have all scripts executed in the database through user "app_user" only, then is there any way to grant necessary privilege or to equip the app_user, so that it will be able to assign the privilege, so we will be able to create the event trigger without need to run the event trigger script from super user itself? This will ensure that we do not need "super user" every time, when we want to run scripts to have an event trigger created for our application schema. Something like "*grant create event trigger on schema app_schema to app_user*"? Regards Yudhi --000000000000b890cd061696e30d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,
We are seeing privilege issues while creating = event triggers. It says the user "must be a superuser to create an = event trigger".

So my question is , if we have application= user as "app_user" which is responsible for creating database ob= jects in schema "app_schema" and also we have all scripts execute= d in the database through user "app_user" only, then is there any= way to grant necessary privilege or to equip the app_user, so that it will= be able to assign the privilege, so we will be able to create the event tr= igger without need to run the event trigger script from super user itself? = This will ensure that we do not need "super user" every time, whe= n we want to run scripts to have an event trigger=C2=A0created for our appl= ication schema.=C2=A0
Something like "grant create event trigge= r on schema app_schema to app_user"?
Regards
Yudhi
--000000000000b890cd061696e30d--