Re: Does PostgreSQL have complete functional test cases?

Hello

2012/11/8 Tianyin Xu <tixu(at)cs(dot)ucsd(dot)edu>:
> Hi, Pavel, Bruce,
>
> Thanks for the explanation!
>
> I have another question regarding the regress test suite.
>
> What does the test result mean to the users/administrators? Are they the
> basic functions that have to be supported by PG server? Or, they are just
> some benchmarks (failure is ok?)

no, there must not be failure!- it is not benchmark

>
> Under certain configuration, I ran the test suite and got several failure
> (see the report below). What does it mean to me? The test results show that
> "regex", "create_index", "inherit", etc, failed (even "select" failed). But
> I still don't know whether these are severe problems to my PG server.

probably you disable some important internal functionality - this
usually means critical problem, because some documented feature is
broken

look to diff file src/test/regress/regression.diffs - and there you
can see, what doesn't work

Regards

Pavel Stehule

>
> (p.s., in the default configuration, all the test suites are passed.)

>
> Best,
> Tianyin
>
> ===============================================
>
> test tablespace ... ok
> test boolean ... ok
> test char ... ok
> test name ... ok
> test varchar ... ok
> test text ... ok
> test int2 ... ok
> test int4 ... ok
> test int8 ... ok
> test oid ... ok
> test float4 ... ok
> test float8 ... ok
> test bit ... ok
> test numeric ... ok
> test txid ... ok
> test uuid ... ok
> test enum ... ok
> test money ... ok
> test rangetypes ... ok
> test strings ... ok
> test numerology ... ok
> test point ... ok
> test lseg ... ok
> test box ... ok
> test path ... ok
> test polygon ... ok
> test circle ... ok
> test date ... ok
> test time ... ok
> test timetz ... ok
> test timestamp ... ok
> test timestamptz ... ok
> test interval ... ok
> test abstime ... ok
> test reltime ... ok
> test tinterval ... ok
> test inet ... ok
> test macaddr ... ok
> test tstypes ... ok
> test comments ... ok
> test geometry ... ok
> test horology ... ok
> test regex ... FAILED
> test oidjoins ... ok
> test type_sanity ... ok
> test opr_sanity ... ok
> test insert ... ok
> test create_function_1 ... ok
> test create_type ... ok
> test create_table ... ok
> test create_function_2 ... ok
> test create_function_3 ... ok
> test copy ... ok
> test copyselect ... ok
> test create_misc ... ok
> test create_operator ... ok
> test create_index ... FAILED
> test create_view ... ok
> test create_aggregate ... ok
> test create_cast ... ok
> test constraints ... ok
> test triggers ... ok
> test inherit ... FAILED
> test create_table_like ... ok
> test typed_table ... ok
> test vacuum ... ok
> test drop_if_exists ... ok
> test sanity_check ... ok
> test errors ... ok
> test select ... FAILED
> test select_into ... ok
> test select_distinct ... ok
> test select_distinct_on ... ok
> test select_implicit ... ok
> test select_having ... ok
> test subselect ... ok
> test union ... ok
> test case ... ok
> test join ... FAILED
> test aggregates ... FAILED
> test transactions ... ok
> test random ... ok
> test portals ... ok
> test arrays ... FAILED
> test btree_index ... ok
> test hash_index ... ok
> test update ... ok
> test delete ... ok
> test namespace ... ok
> test prepared_xacts ... ok
> test privileges ... ok
> test security_label ... ok
> test collate ... ok
> test misc ... ok
> test rules ... ok
> test select_views ... ok
> test portals_p2 ... ok
> test foreign_key ... ok
> test cluster ... ok
> test dependency ... ok
> test guc ... ok
> test bitmapops ... ok
> test combocid ... ok
> test tsearch ... ok
> test tsdicts ... ok
> test foreign_data ... ok
> test window ... ok
> test xmlmap ... ok
> test functional_deps ... ok
> test advisory_lock ... ok
> test json ... ok
> test plancache ... ok
> test limit ... ok
> test plpgsql ... ok
> test copy2 ... ok
> test temp ... ok
> test domain ... ok
> test rangefuncs ... ok
> test prepare ... ok
> test without_oid ... ok
> test conversion ... ok
> test truncate ... ok
> test alter_table ... FAILED
> test sequence ... ok
> test polymorphism ... ok
> test rowtypes ... ok
> test returning ... ok
> test largeobject ... ok
> test with ... ok
> test xml ... ok
> test stats ... FAILED
>
> ========================
> 9 of 131 tests failed.
> ========================
>
>
>
>
>
>
> On Wed, Nov 7, 2012 at 10:00 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
>>
>> 2012/11/7 Bruce Momjian <bruce(at)momjian(dot)us>:
>> > On Tue, Nov 6, 2012 at 09:24:19AM +0100, Pavel Stehule wrote:
>> >> 2012/11/6 Tianyin Xu <tixu(at)cs(dot)ucsd(dot)edu>:
>> >> > Thanks, Pavel!
>> >> >
>> >> > I see. So the regress test cases are the complete functional testing?
>> >> > Am I
>> >> > right?
>> >>
>> >> yes
>> >
>> > Those tests are hardly "complete", as in testing every possible input
>> > and output.
>>
>> sure - but almost all implemented important functionality is covered
>>
>> Pavel
>>
>> >
>> > --
>> > Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
>> > EnterpriseDB http://enterprisedb.com
>> >
>> > + It's impossible for everything to be true. +
>
>
>
>
> --
> Tianyin XU,
> http://cseweb.ucsd.edu/~tixu/