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.96) (envelope-from ) id 1wFt9L-005fd5-0N for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Apr 2026 12:27:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wFt9K-001jMp-0m for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Apr 2026 12:27:18 +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.96) (envelope-from ) id 1wFt9J-001jMh-2d for pgsql-hackers@lists.postgresql.org; Thu, 23 Apr 2026 12:27:17 +0000 Received: from mail-yx1-xb135.google.com ([2607:f8b0:4864:20::b135]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wFt9B-00000002PkD-3XDx for pgsql-hackers@postgresql.org; Thu, 23 Apr 2026 12:27:16 +0000 Received: by mail-yx1-xb135.google.com with SMTP id 956f58d0204a3-6501d242e3fso6371871d50.0 for ; Thu, 23 Apr 2026 05:27:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1776947229; cv=none; d=google.com; s=arc-20240605; b=dMVv1JJjD0vItRQregeL0xi6up8WTxeADe/16041BygYjyQfSEMgBTlX2HdOmCRPi9 +/dIQzhSkeFgvSCxDQBv0yZJrekiCuVtAMvkqfu33/dru3ycQEMF0X2X2zV3pxZFP0/2 LIPVB1IY2BII7ianwweksRxLD3SQlOGsg9ti89+ASd0Icn60czMNQ81rF2VvTeGHCE8Y qinXx474iFmM6Rq1/VeKv94EOYhT7k4B3Y7Q9JHTa0PG/XPMLU25g2OoRx9tqbmFhrKT 1BwKbQ92fn9vvt0900ne4TzuoYvsVfltoyjwHJBtfb24Ms8zGC35r4w+S3bHvC+xe4Y/ go9g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:dkim-signature; bh=4fwKbkOUE4ROF9r9144Gce1W4IGfJM2uGI4XYPEbndQ=; fh=JhLgfoHR15v1klQH7VvzzNZDXiFpw8efEzEGWe0xBhg=; b=jCIKJlMlsiL1ecqvVJaUQvfMEDp0hav4ngObPDAlIg/sr719z8ga5TPtuwx8K0VLHQ aeuTJk9xZryocv4vfl/eObATtO0kmooS9jB6/QKIOrqhq6zwfVOcyvKqem+F/scgMLXz x5enKQBhW9LprOkFcM4BL0Pf4ZhSEFz8dr7QXoR/1tTlQ0CP7pxOd5yfczIc4/OIGiSH Z/tfSIkiF2NUQLWnekoDlGcyPbS++7TnzjwoTcE0fKSroUEmikYBghpHyczCX6rQZjfq pBaveCXcOKHpbsXUzSoqhNBohd6VgW4udQaj73Q6e2+bcQgsL02GYx8t7b5DqvZpv/MI kHFw==; darn=postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1776947229; x=1777552029; darn=postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4fwKbkOUE4ROF9r9144Gce1W4IGfJM2uGI4XYPEbndQ=; b=PCzfuPNG/2cj5u6wRY+qrrux9s8bF27jPaDEvSD/Fslp5AE8UHMZXm15EtIT3/GjAd 0PhGqlKMG/H72SfQigswXCf/zLsihToxbXtPaAhZS9gk4HtI5o/HEwkUfa/RXLhhFNcT GvSItlQamEh0vhFRqz59pdJKCD61C8/yvotZXJ7r2rZ2YcBHLLVh1Wk19dcRGPy62OBt V1SlIM/EhGw5+QyyzHjaNbO/yns5z0iQpCkPA0mHtgWbp+F7J2aQlhIWklJbK7Ugw3Qp QIGOKL25Ub51Csc2Mg6PECYoxzBBw5yDMLua/ADcCZPxzHWNba793yymGAknsuSxS5vn cTdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776947229; x=1777552029; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=4fwKbkOUE4ROF9r9144Gce1W4IGfJM2uGI4XYPEbndQ=; b=QEEshQtfdY4LR4ntyO6nH8XbR87JJ3hIoSq2CbfwoKo9XOZzWxi8Kx4VDUUKCDvLZt s78B+0Ywf3VEIa9+aoKybuGk5fPn6JOkWaTqh56hSI4fYXlNXKnOuHmW6geuqREJplxk 4NXposmUHNDkl9/8j4Rn1+adh5z5153B/ZrBk1/UaD8WqxO9CXYPD/W8QBF62YRchbVD iWNTQ5XOo56PjguDLRDqemi03TB58ULIlgek3BT6m+0AE1zp7X4ZnNZYJhaFrOv1Gklb kHiHFQXlhS56ecXYoLwhH5Pk88nzGkqMMmvi93wdVOpbaTipm+j6xaHO2RFFPM/Qk9Ji R53A== X-Forwarded-Encrypted: i=1; AFNElJ8OkDXsKMWxSQga8SD1WDWOqrWB8agRKE7cVCLSZTk+SiTxOkpLvHvGkIH107X3PDglS4LZ9lpBOHooDgM7@postgresql.org X-Gm-Message-State: AOJu0YwSgjwvhXEWOCt1mGtHf/1FXfXf2ii+W3obUYxLHHGjxjn6RwFJ xnqbaKHOY0KXVzy9XBiRUTzHST0F4QPYoBnLgNnHt/zwmb7vuUHLWxbF5QJZjf1U1+NwzVf9QFh 8CoRsggkBl9kLQkNnZtLTR0E3fLZib7E= X-Gm-Gg: AeBDieses0XNVvn3D3YdF8O1YCmHfWGCJIZCC4zkEiLKxdmNtU4oj66RpvqvWvLQNfm PTY7db5kFXG2t0iTzMyWZGXeNcdOQIVkkCPi3nMbQYeYiFcJZnT02oCMUtLDdQAjuhcV4Ku4898 VKUgJqckP9HeBjBpJJ9y2s73++jRwxFncv9C60L4KHqUHUf3/iToAQJD1ZAAqkK8AR3BDS4V0CZ deACsaEvetIFi8gqt/jC7SWPciZNhLO6wCO+VXJrCoc8q7IvYq2S0XYHX2CVuQysD1rnvRy48Ed xrXsmO6siydcyolvEw== X-Received: by 2002:a05:690e:1c1b:b0:651:c6e0:6bdb with SMTP id 956f58d0204a3-65310810184mr25368632d50.18.1776947229408; Thu, 23 Apr 2026 05:27:09 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:6174:808d:10b0:515:42f4:deed with HTTP; Thu, 23 Apr 2026 05:27:08 -0700 (PDT) In-Reply-To: References: <778F991A-3BF8-4618-8F2E-3C503063F650@yesql.se> From: "David G. Johnston" Date: Thu, 23 Apr 2026 05:27:08 -0700 X-Gm-Features: AQROBzBURHUsuFq37Sw0mrHIdHK22jSXQIT-OPrmsKB_B-_Bd0t8OfoWVhrkXOg Message-ID: Subject: Re: Adding an explaining title to Notes on SGML To: Marcos Pegoraro Cc: Daniel Gustafsson , PostgreSQL Hackers Content-Type: multipart/alternative; boundary="00000000000064c0f406501fc475" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000064c0f406501fc475 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thursday, April 23, 2026, Marcos Pegoraro wrote: > Em qui., 23 de abr. de 2026 =C3=A0s 04:55, Daniel Gustafsson > escreveu: > >> Wouldn't it make more sense to refactor to move the information in the >> note >> closer to what the note is regarding? > > > Also, a note refers to two items in the table, which are bool_and and > bool_or, so what do we do ? Repeat the information ? > Personally, I=E2=80=99d like to do two things here instead of a note. Use = a footnote, but add entries for any/some to the table and use the description to say they are not implemented and to use bool_and/bool_or instead, then anchor the footnote at these entries. That way, people looking for these SQL standard functions actually find them where they expect and understand why they are missing. Index entries wouldn=E2=80=99t hurt. The note actually seems counter-productive for the typical PostgreSQL user who doesn=E2=80=99t even know what is in the standard. And an unintuitive = place to look if you know the function names already. David J. --00000000000064c0f406501fc475 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thursday, April 23, 2026, Marcos Pegoraro <marcos@f10.com.br> wrote:
Em qui., 23 de abr. de 2026 =C3= =A0s 04:55, Daniel Gustafsson <daniel@yesql.se> escreveu:
Wouldn't it make more sense to refactor to move the information in the = note
closer to what the note is regarding?

Also, a note refers to two items in the table, which are bool_and a= nd bool_or, so what do we do ? Repeat the information ?

Personally, I=E2=80=99d like to do two t= hings here instead of a note.=C2=A0 Use a footnote, but add entries for any= /some to the table and use the description to say they are not implemented = and to use bool_and/bool_or instead, then anchor the footnote at these entr= ies.

That way, people looking for these SQL standa= rd functions actually find them where they expect and understand why they a= re missing.=C2=A0 Index entries wouldn=E2=80=99t hurt.

=
The note actually seems counter-productive for the typical PostgreSQL = user who doesn=E2=80=99t even know what is in the standard.=C2=A0 And an un= intuitive place to look if you know the function names already.
<= br>
David J.

--00000000000064c0f406501fc475--