From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Kupershmidt <schmiddy(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Documenting removal of nonnullvalue() and friends |
Date: | 2011-02-27 17:41:59 |
Message-ID: | 201102271741.p1RHfxw06463@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> I thought about this a bit more last night. It's certainly true that
> >> a lot of "internal" functions have comments that don't suggest that
> >> they're not meant to be used directly. What I think would be a good
> >> plan for functions that underlie operators is that we move any useful
> >> comments from pg_proc to pg_operator, and then install a comment in
> >> pg_proc that says "implementation of operator +" (or whatever the
> >> operator name is).
> >> ...
> >> If that sounds like a reasonable plan, I'm willing to have a go at it
> >> after the commitfest closes.
>
> > Tom, any work on this? A TODO?
>
> I haven't done anything about this yet, but it's still on my to-do list.
> Right now (or at least after I finish the patches I'm working on) would
> probably be about the best possible time to do it, since hopefully we
> have the minimum number of unapplied patches that would need to be
> revised to follow the new convention.
Good point.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Serhat Sevki Dincer | 2011-02-27 20:46:37 | minor doc stylesheet patch |
Previous Message | Tom Lane | 2011-02-27 17:40:14 | Re: Documenting removal of nonnullvalue() and friends |