Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 227EE1335B36 for ; Tue, 16 Nov 2010 18:24:44 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 91681-06 for ; Tue, 16 Nov 2010 22:24:37 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mail.postgresql.org (Postfix) with SMTP id 2B5751337B53 for ; Tue, 16 Nov 2010 18:24:36 -0400 (AST) Received: (qmail invoked by alias); 16 Nov 2010 22:24:35 -0000 Received: from a88-115-218-165.elisa-laajakaista.fi (EHLO [10.0.0.101]) [88.115.218.165] by mail.gmx.net (mp042) with SMTP; 16 Nov 2010 23:24:35 +0100 X-Authenticated: #495269 X-Provags-ID: V01U2FsdGVkX1+FpksSHiOFfrxAkDn+79zTXbi8aWmX4kI2Kfgq15 6RS2LCzJ15oThe Subject: Re: Documenting removal of nonnullvalue() and friends From: Peter Eisentraut To: Tom Lane Cc: Robert Haas , Josh Kupershmidt , pgsql-docs@postgresql.org In-Reply-To: <6805.1287239333@sss.pgh.pa.us> References: <1287064806.9532.5.camel@vanquo.pezone.net> <5718.1287094063@sss.pgh.pa.us> <6841.1287098143@sss.pgh.pa.us> <1287156419.9739.1.camel@vanquo.pezone.net> <21407.1287157253@sss.pgh.pa.us> <6805.1287239333@sss.pgh.pa.us> Content-Type: text/plain; charset="UTF-8" Date: Wed, 17 Nov 2010 00:24:34 +0200 Message-ID: <1289946274.31200.74.camel@vanquo.pezone.net> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 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, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201011/30 X-Sequence-Number: 6228 On lör, 2010-10-16 at 10:28 -0400, Tom Lane wrote: > I've occasionally toyed with the idea of moving all non-public > functions > into a separate schema, say "pg_internal", which wouldn't be in the > standard search path (and thus ordinary \df wouldn't see it). That > would be nice from a cleanliness standpoint, but there are downsides > too. Another thing we could do at least for new functions is to name them starting with an underscore (or two).