Re: Documenting removal of nonnullvalue() and friends

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(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-03-03 06:53:05
Message-ID: 27746.1299135185@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

I 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.

Done now.

regards, tom lane

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Thom Brown 2011-03-07 09:57:18 Sync rep doc corrections
Previous Message Robert Haas 2011-03-02 20:58:21 Re: Change to kernel-resources