Re: New regresion test for SET/RESET commnad - Mailing list pgsql-patches

From Tom Lane
Subject Re: New regresion test for SET/RESET commnad
Date
Msg-id 12838.1152680082@sss.pgh.pa.us
Whole thread Raw
In response to New regresion test for SET/RESET commnad  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Responses Re: New regresion test for SET/RESET commnad  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
List pgsql-patches
Zdenek Kotala <Zdenek.Kotala@Sun.COM> writes:
> I created new regression test for check SET and RESET commands and
> configuration subsystem.

Does this actually accomplish anything?  The checks that retail SETs
and RESETs work seem redundant with numerous existing tests.  The SELECT
from pg_settings is a seriously bad idea: it adds 100K of bloat to the
regression files, tests nothing of great interest, and will cause
regression test failures under a large variety of scenarios (eg, initdb
chose less-than-max shared memory settings, or we're doing "make
installcheck" against an installed server with even one nondefault
parameter setting).  Not to mention the extra maintenance effort of
updating this expected file anytime anyone changes guc.c at all,
even to the extent of fixing grammar in a GUC-variable description.

            regards, tom lane

pgsql-patches by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: reply to ...
Next
From: Neil Conway
Date:
Subject: Re: [patch 0/9] annual pgcrypto update