Re: count_nulls(VARIADIC "any") - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: count_nulls(VARIADIC "any")
Date
Msg-id 56A221E8.4000602@BlueTreble.com
Whole thread Raw
In response to Re: count_nulls(VARIADIC "any")  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: count_nulls(VARIADIC "any")  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On 1/21/16 1:48 PM, Pavel Stehule wrote:
>     the form of regress tests is not pretty significant issue. Jim's
>     design is little bit transparent, Marko's is maybe little bit
>     practical. Both has sense from my opinion, and any hasn't
>     significant advantage against other.
>
>
> any possible agreement, how these tests should be designed?
>
> simple patch, simple regress tests, so there are no reason for long waiting.

I don't really see how individual tests are more practical (you can 
still cut and paste a table...), but since there's no strong consensus 
either way I'd say it's up to you as author.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fwd: Re: [DOCS] Document Upper Limit for NAMEDATELEN in pgsql 9.5+
Next
From: Jim Nasby
Date:
Subject: Re: proposal: PL/Pythonu - function ereport