From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [bugfix] sepgsql didn't follow the latest core API changes |
Date: | 2012-09-05 13:49:09 |
Message-ID: | 50475855.6010504@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/05/2012 09:11 AM, Alvaro Herrera wrote:
> Excerpts from Kohei KaiGai's message of mié sep 05 08:30:37 -0300 2012:
>> 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?
> Yes, regression test diffs are also reported and can cause failures.
> As far as I know, you can construct your own test steps, if you want to
> do something customized that's not present in regular BF animals.
Looking at SEPgsql testing is on my long TODO list. I'll have to set up
a separate VM for it, as I don't habitually run SELinux.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | boy | 2012-09-05 13:57:12 | BUG #7521: Cannot disable WAL log while using pg_dump |
Previous Message | Andrew Dunstan | 2012-09-05 13:46:48 | Re: pg_upgrade diffs on WIndows |