Horton

Re: sepgsql contrib module

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Kohei Kaigai <Kohei.Kaigai@eu.nec.com>, Stephen Frost <sfrost@snowman.net>, KaiGai Kohei <kaigai@kaigai.gr.jp>, PgHacker <pgsql-hackers@postgresql.org>
Date: 2011-02-15T15:50:19Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. pgindent run for 9.0, second run


On 02/15/2011 10:34 AM, Robert Haas wrote:
> On Mon, Feb 14, 2011 at 9:55 PM, Tom Lane<tgl@sss.pgh.pa.us>  wrote:
>> On the whole, I don't think that sepgsql-regtest.pp should be built or
>> installed at all during the build phase.  It ought to be generated
>> during regression test startup, instead.
> You have to manually install and enable it before you can run the
> regression tests.  This is documented.
>

That's not the point. Right now you can't even run just a postgresql 
build on a machine that doesn't have selinux enabled, let alone run the 
regression tests. And if we construct the regression gadget at 
postgresql build time, who is to say it has the right settings for the 
run time environment, given that the build is apparently dependent on a 
runtime kernel setting?

cheers

andrew