Re: [bugfix] sepgsql didn't follow the latest core API changes - Mailing list pgsql-hackers

From Kohei KaiGai
Subject Re: [bugfix] sepgsql didn't follow the latest core API changes
Date
Msg-id CADyhKSVhtfwfhRA8_4Z_XZoWmhJLSEXGzu01-M7U+Ko+dQdBtQ@mail.gmail.com
Whole thread Raw
In response to Re: [bugfix] sepgsql didn't follow the latest core API changes  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [bugfix] sepgsql didn't follow the latest core API changes  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
2012/9/3 Alvaro Herrera <alvherre@2ndquadrant.com>:
> Excerpts from Kohei KaiGai's message of dom sep 02 15:53:22 -0300 2012:
>> This patch fixes a few portions on which sepgsql didn't follow the latest
>> core API changes.
>
> I think you should get a buildfarm animal installed that builds and
> tests sepgsql, to avoid this kind of problem in the future.
>
Thanks for your suggestion. I'm interested in.

http://wiki.postgresql.org/wiki/PostgreSQL_Buildfarm_Howto

Does it test only build-correctness? Or, is it possible to include
result of regression test for result to be alarmed?
-- 
KaiGai Kohei <kaigai@kaigai.gr.jp>



pgsql-hackers by date:

Previous
From: Gianni Ciolli
Date:
Subject: Re: State of the on-disk bitmap index
Next
From: Daniel Bausch
Date:
Subject: Re: State of the on-disk bitmap index