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 1uqa8r-008yO3-It for pgsql-general@arkaria.postgresql.org; Mon, 25 Aug 2025 16:33:58 +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 1uqa8p-00BRZ1-Rk for pgsql-general@arkaria.postgresql.org; Mon, 25 Aug 2025 16:33:56 +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 1uqa8p-00BRY5-Gf for pgsql-general@lists.postgresql.org; Mon, 25 Aug 2025 16:33:56 +0000 Received: from mail-oo1-xc2e.google.com ([2607:f8b0:4864:20::c2e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uqa8n-001n98-0c for pgsql-general@lists.postgresql.org; Mon, 25 Aug 2025 16:33:55 +0000 Received: by mail-oo1-xc2e.google.com with SMTP id 006d021491bc7-61dd3b5cdd7so411366eaf.1 for ; Mon, 25 Aug 2025 09:33:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1756139631; x=1756744431; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=d0rjaVHrRTtgv0MFYDURktLKeDrxqH2pCehM8iND5XE=; b=MZdWhLlIXtFTZk7bF8Ro4MhgwtxQvREvl8n7wIOKOIZze1tSk8ATxmav68LVcWhEsn 3mS3icQ0s3CPpRhaXCRWn4xRbgQU0oQ3J97O9gpuVMZsYNYnArt/y68oHEl/GpDzM9ou n5nyf1kBFmkAHKpD5EIOLFvVblDUBEVhEXTEvv3KlBnARpA0yVSRn1qNXYcsuH1jvejM jGkls6lGfKWZxHVO8y61MH+KbqyxfkRUv/AltKxmjJRlnPgEqSUfrVHul/XkWkKM4RUa p1s6sVeGIrrcP6cUf7sYEHe7/m0wkTJlQoKDRhqodU7kcHRowejG00KWgItFM+824GXz Xj3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1756139631; x=1756744431; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=d0rjaVHrRTtgv0MFYDURktLKeDrxqH2pCehM8iND5XE=; b=n2Dp6yqI29hmm+iW6JD+9y6ZxLcau1CdeOD9iGk5WTMfh6tpiMyMIYQ7zq7ov84vpv D/4z/I3KpdFyJ3LNMmPPrCdOiV3wwbkUrYO7qHSKUoehy0CFCa7LvREOg9Gad+0YWGmH dzJY/TolRkg2P8aBXC1ErQ0TZMss/MCAKl+79XOXWKXPrU9AU7enCCdR5ac4rRADH3Za xF+Y6ZQrpRXzC8SbE675vioiRD4cIET2arHMTk5Vo+X8GNXAvVYS2p85dPTQc5kXp1yi gctQE6jsw67xy09Xc+Z+rSXAA3wzf5SrHZVSwOpWko2IUU2tnzyLgT71wI4uqgRvSrjr VZrA== X-Gm-Message-State: AOJu0Yzt6hDtJkC9Yk3lSHvc/+W4upY+fwKm/n8xkOXpF/VoG4OolsZi ugapuMgsHusKh31ezy4zvjKo3fmY8nkJZ7Gmxp8+LP8j61/97wmiCSFMkkIyL/VTvH9seW1Bcc3 t5kHpxUuo2SMk35k5unkO0FJsJbhTjIMPQg== X-Gm-Gg: ASbGncthKsuHwGFyLpxeCTY0UweyGgAuRbQCAld+RkKruVtyPjFLTQmgVGwfJBDfbWL 514vfqjvC279tIt+Kl0lqGgNWghexO5hT4G5mRJYAaDIv6hbW9avKmsM7eJW/mbx681/sJSUwGR vwXG9nC+rhh96gFZIWOb6xtVfeBCPM75CRwtyFti+8oECCeknVjogyvSi37BMyklzCG8QzYzMZp Y4HHe58MA== X-Google-Smtp-Source: AGHT+IF8zxEOof6kzx08892YIKdljJhO1I7eT6Ys3Acn9Oda8oDsDmZuP9AJ8lW9MOp4icGHHjH8/DoPr20cBELE78Q= X-Received: by 2002:a05:6808:4f6a:b0:434:f62:6905 with SMTP id 5614622812f47-437853322fdmr7045218b6e.26.1756139630939; Mon, 25 Aug 2025 09:33:50 -0700 (PDT) MIME-Version: 1.0 References: <3a6e840a-5c30-4eed-9e5b-474dafc6c29f@aklaver.com> In-Reply-To: <3a6e840a-5c30-4eed-9e5b-474dafc6c29f@aklaver.com> From: Dominique Devienne Date: Mon, 25 Aug 2025 18:33:39 +0200 X-Gm-Features: Ac12FXzHngHsZTnPWN_9ZFDxd_TOrKSoCF1qdQeRDhI0w4W0nTFqa2hnxIMPlok Message-ID: Subject: Re: DISABLE TRIGGER doc wrong? To: Adrian Klaver Cc: pgsql-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Aug 25, 2025 at 6:24=E2=80=AFPM Adrian Klaver wrote: > On 8/25/25 09:19, Dominique Devienne wrote: > > or I'm reading it wrong? --DD > > > > From https://www.postgresql.org/docs/current/sql-altertable.html#SQL-A= LTERTABLE-DESC-DISABLE-ENABLE-TRIGGER: > >> Disabling or enabling internally generated constraint triggers require= s superuser privileges > > > > We were disabling triggers as the owner of the table just fine, no > > SUPERUSER involved. So is the doc out-of-date? > > From the sentence before the above: > > "... internally generated constraint triggers, such as those that are > used to implement foreign key constraints or deferrable uniqueness and > exclusion constraints)." And? I don't see your point Adrian. Has no bearing on the SUPERUSER requirement, in my reading.