Re: security label support, revised - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: security label support, revised
Date
Msg-id 1285685780.20420.4.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: security label support, revised  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On tis, 2010-09-28 at 09:22 -0400, Robert Haas wrote:
> > I think it should actually be run as part of the regular build.
>  Ever
> > since I started using git and developing like 10 features at once,
> and
> > other people doing the same, the chances of (hidden) OID conflicts
> is
> > growing immensely.
> 
> Injecting nonessential checks into the build process doesn't seem like
> a good idea to me.  Typing 'make' should just do the build.  If you
> want to check for breakage, well, that's what 'make check' is for.

I don't feel strongly either way, but if we want to philosophize for a
minute, all these -W option on the compiler command line are
nonessential checks. ;-)  I suppose 'make check' should test whether the
code behaves correctly rather than checking whether the code was
structured consistently to begin with.



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Proposal: plpgsql - "for in array" statement
Next
From: Tom Lane
Date:
Subject: Re: small fix to possible null pointer dereference in byteaout() varlena.c