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 1sVtrk-00CE6n-NE for pgsql-docs@arkaria.postgresql.org; Mon, 22 Jul 2024 14:18:16 +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 1sVtri-002l0k-Rq for pgsql-docs@arkaria.postgresql.org; Mon, 22 Jul 2024 14:18:15 +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 1sVtbZ-002Tpe-Qq for pgsql-docs@lists.postgresql.org; Mon, 22 Jul 2024 14:01:34 +0000 Received: from mail-wr1-x435.google.com ([2a00:1450:4864:20::435]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sVtbX-000t3Q-IU for pgsql-docs@lists.postgresql.org; Mon, 22 Jul 2024 14:01:33 +0000 Received: by mail-wr1-x435.google.com with SMTP id ffacd0b85a97d-368526b1333so1694050f8f.1 for ; Mon, 22 Jul 2024 07:01:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721656890; x=1722261690; darn=lists.postgresql.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=vmUUkUCovnsxR8g7c4wUcn2XixU+b/xsQqrraqEkuDU=; b=C/TObqf1/F7eA8ISFgJGXk/sJJK/6ywz+whfKlkVO52Yl4OTw0yki5s+azY85JVxIH 5/pdxY6PYdWulT8nzLHSyQQP7zIyCVK+uVF3LkCAkrYGoof6dzPjmpzTkOcx+8mvD0Sl vBhtaieqUW43q8PAmeeSqLEEZ0Pb9a396XQtMIM9r96fie2O/p4LZMhyz6t7T+IWA7ph 6CEWgrzEUj8/XZ9nfkDgXfA4y0XVBkKp2/hqwJ/KHtF9LLrVHx+GscI9dq6poovbOwpp 4QmZJ7CjRVP7xsDDCx68DIBs4uqyy5g37QSX+ZZodTzZEmSYlu6FxslJYbeg9ZX8lOR+ t0Ng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721656890; x=1722261690; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=vmUUkUCovnsxR8g7c4wUcn2XixU+b/xsQqrraqEkuDU=; b=HCznZiJmCQoxWu3kO+0hGcmw0pY4fH4PvPkwseLxsnKHFH9TEsuLWG2TjxmXSFzDOT b4Sny9GA9pkz5msxbm2YHdOtATXNXO+l6KbQWxGehvD8hW4A+cyRIyhkMl2cJ799bkiI s9aSPkRijg+KD0am/hmjEXwDCNUTNKeSwal8XyySTliHxleAfC2VBeFVb3skq213kJuO NSHnAel4bXctJH8Ul4lFqbLsrROZEZJSK2jQY/ySX1ouW3oEw3LLJalR9uKW+NGN7hlU gT2KO8ybNuglT4lC7fTNDsl1BngIJGPTZ/pPk6NtMcQry2UrY7xkXokoHlPcpUuMfNft x7gA== X-Gm-Message-State: AOJu0YwsrwrVWbHJ/FZBrDJBm3NY8czgrjjQfTKVDUuO4fHJn7oXrilG pWfroLj7SpYxPmdTFZM/U9rUpui8mwSRm6X7EajLSfoJFHNA1O6ftB2fZg== X-Google-Smtp-Source: AGHT+IG4+PQp/Jd4GTUS/ykD4AkQ+nnldk3udj65nGU1lMF/A+Y11y4vs/ZwEqMOWhUXWOazrxKrsw== X-Received: by 2002:adf:a3c8:0:b0:368:4488:66f8 with SMTP id ffacd0b85a97d-36873f18f12mr6458133f8f.23.1721656889739; Mon, 22 Jul 2024 07:01:29 -0700 (PDT) Received: from smtpclient.apple ([2a02:121f:3ed6:0:e012:268b:d0c9:55bc]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-427d2a7257esm154615975e9.28.2024.07.22.07.01.29 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jul 2024 07:01:29 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\)) Subject: Re: Undocumented := alternative in using option of raise statement From: Philipp Salvisberg In-Reply-To: Date: Mon, 22 Jul 2024 16:01:18 +0200 Cc: pgsql-docs@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <172163522625.709.14011263605748671820@wrigleys.postgresql.org> To: jian he X-Mailer: Apple Mail (2.3774.600.62) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 22 Jul 2024, at 15:18, jian he wrote: >=20 > On Mon, Jul 22, 2024 at 8:38=E2=80=AFPM PG Doc comments form > wrote: >>=20 >> The following documentation comment has been logged on the website: >>=20 >> Page: = https://www.postgresql.org/docs/16/plpgsql-errors-and-messages.html >> Description: >>=20 >> The using option is documented as follows for all variants of the = raise >> statement: >>=20 >> USING option =3D expression [, ... ] >>=20 >> However, since "do $$ begin raise notice using message :=3D 'foo'; = end $$;" >> works and the alternative to "=3D" is documented in >> = https://www.postgresql.org/docs/current/plpgsql-statements.html#PLPGSQL-ST= ATEMENTS-ASSIGNMENT >> I suggest to change the grammar to >>=20 >> USING option { :=3D | =3D } expression [, ... ] >>=20 >> for the raise statement. >=20 > I think this has been committed. > = https://git.postgresql.org/cgit/postgresql.git/commit/?id=3D56c6be57af6bd1= c7eb7dff50e5f169ced4ed3045 >=20 > you can check latest doc at: > https://www.postgresql.org/docs/devel/plpgsql-errors-and-messages.html Thanks Jan for letting me know. Looks good.=20 Next time I'll check the devel version of the docs before submitting a = correction.=