Re: pg_upgrade and extra_float_digits

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade and extra_float_digits
Date: 2010-05-17 02:44:51
Message-ID: 3142.1274064291@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> This whole discussion leads me to the conclusion that we need to look
> more imaginatively at our testing regime. When the buildfarm was created
> it (via pg_regress) covered a lot of what we needed to test, but that is
> becoming less and less true. Not only does pg_upgrade need testing but
> we need to devise some sort of automated testing regime for SR and HS,
> among other things. pg_regress is showing it's age a bit, I think.

The regression tests have never pretended to test more than a fraction
of what might be interesting to test. Crash recovery, in particular,
has always been interesting and has never been tested in any mechanized
way. They don't really exercise concurrent behavior in any meaningful
way either. I don't think they're "showing their age" so much as we're
starting to get more ambitious about what we would like to have routine
testing for.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2010-05-17 02:51:13 Re: Keepalive for max_standby_delay
Previous Message Andres Freund 2010-05-17 02:40:36 Re: Sort of a planner regression 8.3->8.4 (due to EXISTS inlining) and related stuff