From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp>, KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: security label support, revised |
Date: | 2010-09-28 12:03:06 |
Message-ID: | 1285675386.20420.1.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On tis, 2010-09-28 at 13:53 +0200, Magnus Hagander wrote:
> On Tue, Sep 28, 2010 at 13:50, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > On Tue, Sep 28, 2010 at 3:57 AM, Shigeru HANADA
> >> The src/include/catalog/duplicate_oids script reports that 3037 ~
> >> 3040 are used two or more times.
> >>
> >> Though all regression tests finish successfully, should this be
> >> fixed ?
> >
> > Woops. Thanks for the report, fixed. I wish we had a regression test
> > that would catch these mistakes. It's easy to forget to run this
> > script.
>
> Could we run the script as part of the regression tests? :-)
>
> Or if not, could we have the buildfarm run it?
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2010-09-28 12:45:30 | Re: Proposal: plpgsql - "for in array" statement |
Previous Message | Magnus Hagander | 2010-09-28 11:53:34 | Re: security label support, revised |