From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: libpq URI and regression testing |
Date: | 2012-04-17 18:47:55 |
Message-ID: | 1334688384-sup-4194@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Peter Eisentraut's message of mar abr 17 15:41:04 -0300 2012:
> On tis, 2012-04-17 at 10:47 -0300, Alvaro Herrera wrote:
> > What's the preferred way to make it automatically tested as much as
> > possible? I know the buildfarm does not run "installcheck-world", so if
> > we want it there, it'd need a bit more code on the client side. I think
> > it would be wise to have it also run on installcheck-world.
>
> It was agreed during the patch discussion that it shouldn't be run
> automatically.
Oh, okay. I didn't notice that. I guess we should issue a
call-for-testing, then, so that we ensure it works (FSVO works) in all
(FSVO all) platforms.
> > Hmm. Just had this thought: not all platform support the same socket
> > types. Maybe we should have separated the .in file in three parts:
> > IPv4, IPv6, unix-domain socket. That way each platform would only run
> > tests that pertain to it. Right now there's a single "regress.in" file
> > that lists all the tests.
>
> That's one reason for that, but there are probably others in the way of
> making this fully portable and automatable.
Hmm.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2012-04-17 19:01:29 | Re: Parameterized-path cost comparisons need some work |
Previous Message | Robert Haas | 2012-04-17 18:46:23 | Re: Parameterized-path cost comparisons need some work |