| From: | Alex <ash(at)commandprompt(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: libpq URI and regression testing |
| Date: | 2012-04-18 21:08:24 |
| Message-ID: | 874nsgsq7r.fsf@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> 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.
Hm... the testing program we've actually committed avoids any connection
attempts and only deals with testing the parser routine. Does it change
that?
--
Regards,
Alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex | 2012-04-18 21:13:17 | Re: libpq URI and regression testing |
| Previous Message | Robert Haas | 2012-04-18 20:09:45 | buffer locking fix for lazy_scan_heap |