On Oct 23, 2015, at 9:26 AM, Jim Nasby wrote:
> I would love it if make check worked. make installcheck adds extra effort to
> extension develoopment, not to mention leaving your actual install in a less
> than pristine state.
I’ve wanted this for a long time. I think it would have to create a
On 10/23/15 11:02 AM, Heikki Linnakangas wrote:
On 10/23/2015 02:59 PM, Michael Paquier wrote:
On Fri, Oct 23, 2015 at 7:46 PM, Heikki Linnakangas wrote:
On 10/23/2015 01:33 PM, Sandro Santilli wrote:
In short, I don't think just setting extensions_path is enough or
desirable,
but I would welco
On 10/23/2015 02:59 PM, Michael Paquier wrote:
On Fri, Oct 23, 2015 at 7:46 PM, Heikki Linnakangas wrote:
On 10/23/2015 01:33 PM, Sandro Santilli wrote:
In short, I don't think just setting extensions_path is enough or desirable,
but I would welcome a patch that makes "make check" work for exten
On Fri, Oct 23, 2015 at 7:46 PM, Heikki Linnakangas wrote:
> On 10/23/2015 01:33 PM, Sandro Santilli wrote:
> In short, I don't think just setting extensions_path is enough or desirable,
> but I would welcome a patch that makes "make check" work for extensions, by
> creating a temporary installatio
23.10.2015, 13:33, Sandro Santilli kirjoitti:
One problem we have with PostGIS is you cannot test an extension
unless you have access to the system extension dir.
The following patch tries to address that by allowing to specify
a per-cluster extension path via an "extensions_path" GUC.
It is mo
On 10/23/2015 01:33 PM, Sandro Santilli wrote:
One problem we have with PostGIS is you cannot test an extension
unless you have access to the system extension dir.
The following patch tries to address that by allowing to specify
a per-cluster extension path via an "extensions_path" GUC.
It is m
