I would suggest to add that to https://wiki.postgresql.org/wiki/Todo.
I may look into it when I have time, over the summer. The key point is
that there is no need for a temporary installation, but only of a
temporary cluster, and to trick this cluster into loading the
uninstalled extension,
On Jun 15, 2014, at 12:25 AM, Fabien COELHO coe...@cri.ensmp.fr wrote:
I'm not sure the extension is sought for in the cluster (ie the database data
directory). If you do make install the shared object is installed in some
/usr/lib/postgresql/... directory (under unix), and it is loaded from
That does not mean that it starts a new cluster on a port. It means it
will test it against an existing cluster after you have installed into
that cluster.
Yes, that is what I was saying.
It invokes psql which is expected to work directly. Note that there
is no temporary installation, it
On Jun 12, 2014, at 11:40 PM, Fabien COELHO coe...@cri.ensmp.fr wrote:
I would suggest to add that to https://wiki.postgresql.org/wiki/Todo.
I may look into it when I have time, over the summer. The key point is that
there is no need for a temporary installation, but only of a temporary
Andres said during the unconference last month that there was a way to
get `make check` to work with PGXS. The idea is that it would initialize
a temporary cluster, start it on an open port, install an extension, and
run the extension's test suite. I think the pg_regress --temp-install,
On Jun 12, 2014, at 11:28 AM, Fabien COELHO coe...@cri.ensmp.fr wrote:
My 0.02€: It is expected to work, more or less, see the end of
http://www.postgresql.org/docs/9.3/static/extend-pgxs.html
That says:
“The scripts listed in the REGRESS variable are used for regression testing of
your
Hackers,
Andres said during the unconference last month that there was a way to get
`make check` to work with PGXS. The idea is that it would initialize a
temporary cluster, start it on an open port, install an extension, and run the
extension's test suite. I think the pg_regress
