Re: [bugfix] sepgsql didn't follow the latest core API changes

From: Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [bugfix] sepgsql didn't follow the latest core API changes
Date: 2012-09-05 11:30:37
Message-ID: CADyhKSVhtfwfhRA8_4Z_XZoWmhJLSEXGzu01-M7U+Ko+dQdBtQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2012/9/3 Alvaro Herrera <alvherre(at)2ndquadrant(dot)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(at)kaigai(dot)gr(dot)jp>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Bausch 2012-09-05 11:37:59 Re: State of the on-disk bitmap index
Previous Message Gianni Ciolli 2012-09-05 10:42:22 Re: State of the on-disk bitmap index