Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 29A6D1337FCC for ; Thu, 14 Oct 2010 11:38:58 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 69138-06 for ; Thu, 14 Oct 2010 14:38:48 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 554661337F7E for ; Thu, 14 Oct 2010 11:38:13 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o9EEcBEu018057; Thu, 14 Oct 2010 10:38:11 -0400 (EDT) To: Josh Kupershmidt cc: Peter Eisentraut , Robert Haas , pgsql-docs@postgresql.org Subject: Re: Documenting removal of nonnullvalue() and friends In-reply-to: References: <1287064806.9532.5.camel@vanquo.pezone.net> Comments: In-reply-to Josh Kupershmidt message dated "Thu, 14 Oct 2010 10:29:42 -0400" Date: Thu, 14 Oct 2010 10:38:11 -0400 Message-ID: <18056.1287067091@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201010/24 X-Sequence-Number: 6165 Josh Kupershmidt writes: > I'm curious now, though: are there any other functions which we're > leaving intentionally undocumented? Practically all the functions underlying operators are undocumented, eg int4pl(int, int). (If you consider IS NOT NULL to be an operator, then nonnullvalue is exactly one of those.) It's possible for people to use those directly but it's discouraged. I do *not* want to add them to the docs, because (a) I do *not* want people to use them directly and (b) there are a hell of a lot of them, so the docs would get much much longer with no actual added value. Perhaps what we should really add to the docs is a statement that use of undocumented functions is deprecated and we will not be responsible when your code breaks because one of those is changed or removed. regards, tom lane