Re: [COMMITTERS] pgsql: make_restrictinfo() failed to attach

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: make_restrictinfo() failed to attach
Date: 2005-11-21 22:28:37
Message-ID: 43824A15.60700@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Jim C. Nasby wrote:

>isn't a test for a specific
>case better than none at all? Is the concern how long make check takes?
>
>

It shouldn't be, since we can (and do) have multiple regression test
sets. If there are tests that take too long for normal use, let's make a
"takes a long time" set and a new Makefile target for it - we'll add it
to the buildfarm suite so automated testing (which shouldn't care how
long it takes) will do the heavy work for us.

cheers

andrew

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message User Gsmet 2005-11-21 22:43:02 pgfouine - pgfouine: add common LOG line that should be ignored
Previous Message User Gsmet 2005-11-21 22:23:44 pgfouine - pgfouine: ignore common errors

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2005-11-21 22:35:15 Re: Heading to Mexico
Previous Message Bob Ippolito 2005-11-21 22:24:21 Re: PostgreSQL 8.1.0 catalog corruption