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 1uqZuy-008tF1-Ea for pgsql-general@arkaria.postgresql.org; Mon, 25 Aug 2025 16:19:37 +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 1uqZux-00BBWw-Ru for pgsql-general@arkaria.postgresql.org; Mon, 25 Aug 2025 16:19:36 +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 1uqZux-00BBWn-Gy for pgsql-general@lists.postgresql.org; Mon, 25 Aug 2025 16:19:36 +0000 Received: from mail-ot1-x32b.google.com ([2607:f8b0:4864:20::32b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uqZuv-001n0o-17 for pgsql-general@lists.postgresql.org; Mon, 25 Aug 2025 16:19:35 +0000 Received: by mail-ot1-x32b.google.com with SMTP id 46e09a7af769-7452b3a0b31so189417a34.0 for ; Mon, 25 Aug 2025 09:19:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1756138771; x=1756743571; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ti7J4rbQaCkdrgCPUBKf8NtrF/gj1AdbpgBBoHDyHyE=; b=GwmLs7iTdFAYzsN+hYpUR5HhArga9TchjwO/41uGo8jIgQnliPX18wglem4GqgFLDB TtIiCnVqM6/UvhpxUjqDumeVrX3/9wIcKa8IGU1PQCNoWs6hs1wRfSRl7Ag7p3WdSqpg hznO1qGc8iZ+8HlO8XPfs9z5XL9RjwmxMLxF+7pW2nyZYV+/Inr2q3/XKqCpdpmEIZMF wXuwXCaH3koWgpVyMNzcP5Ta59k+th6w2X8+F1hCuvJDfIVemz2R2J09kWr8SYPj/dWs SyH6Z4FRWQIxsxw1lQ1T4fyvYEFN2zhBK16ShkQJhICToMN9YBQJU2n2uWvIyK7Wh40+ z+Jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1756138771; x=1756743571; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ti7J4rbQaCkdrgCPUBKf8NtrF/gj1AdbpgBBoHDyHyE=; b=wwZU7Q8NyobM4ILV3GDXia+HnTfSnfjVbynQpTYfs0sbEI6WJpG3PfKMCeNjY+FiTr nGi5zjllQx93xhwHQyCxrjC1vCYgKSlo0Xp1YpuFHxYYjxe8VuU15FfJY9H+IB0SNkPQ d067Kq9xZBtoqm8SXoW3/CpXMvgJw17D4XZe/HDClDpEkxJ4qArvDTd23dK1tmO08hsv GfoLenMmFAUFBlIaUd9Oxz2lfWBw23v4ftNbr5RXmsy7vNXIcvMoHNnXz6ppxffujTxM WRh8shApREqHLejOUS3MGLNTXqiYlVpUeUnkLHVUSRb2aHz6WFfvK/+1IvbthqS3b7JF Ldsw== X-Gm-Message-State: AOJu0YzkIWk8cumMRlAAjpW0M3Qy7LrU6fbxdwdryj+LjZB02Tii4N6g WLN7IqwAf+gM/U4IVwv4HoccyEXeheWTY0/ehQp48EpGUt+yXySfTQDLhdtTmlwqxACznOIytPf 7JFfq6trAC2SzCrU3A5d8VCWE10SFDEyg7qd/ X-Gm-Gg: ASbGnculqiAUGeBnRa32Oyus8ORfdxGDNGEmjX30st1cilV8hnWVh1JwScgEhiJX82n IY7q5EN70VVYjz+1MMIspqvEG0uBNb+pnqOkMzU6Px4nnKejEE8FxF7drR6zWmoGPy6xgz6vkUB ZdN6uKgMi+APUcd5XYpBW7vZ0vhcO3+ANt3AmZx26Fi2Kw1hV++c/mbO1rMiYKLPiRD3HqB4b6Z nt2t0p/Eg== X-Google-Smtp-Source: AGHT+IE3+GdH58iMwzF4tyvFji3Oo5Rizek8DAhRBLUNuXMuKAdTbl9cExPPVJ7zHeKOLZQWGmvNg21pZ3mVaSGDAJE= X-Received: by 2002:a05:6808:508b:b0:435:7445:9b54 with SMTP id 5614622812f47-43785272d3fmr5150559b6e.7.1756138771140; Mon, 25 Aug 2025 09:19:31 -0700 (PDT) MIME-Version: 1.0 From: Dominique Devienne Date: Mon, 25 Aug 2025 18:19:19 +0200 X-Gm-Features: Ac12FXw-51YlpwdfWAX0Qco77uMG2l5CjbyyQOSnHPW-anpnGBPJlJL1gpJUzPc Message-ID: Subject: DISABLE TRIGGER doc wrong? To: pgsql-general@lists.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 or I'm reading it wrong? --DD From https://www.postgresql.org/docs/current/sql-altertable.html#SQL-ALTERTABLE-DESC-DISABLE-ENABLE-TRIGGER: > Disabling or enabling internally generated constraint triggers requires superuser privileges We were disabling triggers as the owner of the table just fine, no SUPERUSER involved. So is the doc out-of-date? PS: By mistake... We were ALTER TABLE {}.{} DISABLE TRIGGER ALL when we meant ALTER TABLE {}.{} DISABLE TRIGGER USER