Re: new json funcs - Mailing list pgsql-hackers

From Tom Lane
Subject Re: new json funcs
Date
Msg-id 14851.1389380331@sss.pgh.pa.us
Whole thread Raw
In response to Re: new json funcs  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: new json funcs
Re: new json funcs
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 01/10/2014 01:27 PM, Tom Lane wrote:
>> See commits 94133a935414407920a47d06a6e22734c974c3b8 and
>> 908ab80286401bb20a519fa7dc7a837631f20369.

> OK, I can fix that I guess.

Sure, just remove the DESCR comments for the functions that aren't meant
to be used directly.

I don't think this is back-patchable, but it's a minor point, so at least
for me a fix in HEAD is sufficient.

I wonder whether we should add an opr_sanity test verifying that operator
implementation functions don't have their own comments?  The trouble is
that there are a few that are supposed to, but maybe that list is stable
enough that it'd be okay to memorialize in the expected output.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Florian Pflug
Date:
Subject: Re: [PATCH] Negative Transition Aggregate Functions (WIP)
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Standalone synchronous master