ne died suddenly. I'm getting the following test
> failure
>reliably on the new one. I don't know much about postgresql
> setup, so
>I'd appreciate any advice.
>
># -*
my
previous one died suddenly. I'm getting the following test
failure
reliably on the new one. I don't know much about postgresql
setup, so
I'd appreciate any advice.
# -*- compil
tly had to move development to a new laptop because my
previous one died suddenly. I'm getting the following test failure
reliably on the new one. I don't know much about postgresql setup, so
I'd appreciate any advice.
I'm getting the following test failure
reliably on the new one. I don't know much about postgresql setup, so
I'd appreciate any advice.
# -*- compilation -*-
250. get-data-psql.at:147: testing GET DATA /TYPE=PSQL ...
../../te
e
thoughts.
On Sat, Jan 19, 2019 at 06:28:08PM +, Jeremy L wrote:
> Haven't looked at the bootstrapping from pspp, but have some experience with
> postgres connections.
>
> Postgresql generally requires a database to exist on the cluster on the
> server for the client to con
Haven't looked at the bootstrapping from pspp, but have some experience
with postgres connections.
Postgresql generally requires a database to exist on the cluster on the
server for the client to connect to. There may be a system-provided
"postgres" database you can use, then c
I've recently had to move development to a new laptop because my
previous one died suddenly. I'm getting the following test failure
reliably on the new one. I don't know much about postgresql setup, so
I'd appreciate any advice.
# -*- compilati
On Fri, Aug 19, 2016 at 10:48:52PM +0200, Harry Thijssen wrote:
> I am looking again in the postgresql issue when cross-compiling.
>
>
> 2016-03-18 21:23 GMT+01:00 John Darrington :
>
> > On Fri, Mar 18, 2016 at 08:53:09PM +0100, Harry Thijssen wrote:
> > Hi
I am looking again in the postgresql issue when cross-compiling.
2016-03-18 21:23 GMT+01:00 John Darrington :
> On Fri, Mar 18, 2016 at 08:53:09PM +0100, Harry Thijssen wrote:
> Hi
>
> It seems to me that the test for Postgresql in configure is not
> correct.
>
&g
Re: Friedrich Beckmann 2016-04-12 <[email protected]>
> Hi Christoph,
>
> thanks for the info. We had disabled the optional postgresql on hurd-i386 in
> the previous pspp release.
>
> Is it maybe an idea to include this test case in the reg
Just for clarification ...
As correctly mentioned, the PostgreSQL server cannot run on the Hurd.
However this does not mean that the PSPP postgres client option cannot or
should not be enabled
on the Hurd. It simply means that the regression test for that option cannot
run.
My recollection
Hi Christoph,
thanks for the info. We had disabled the optional postgresql on hurd-i386 in
the previous pspp release.
Is it maybe an idea to include this test case in the regression in postgresql?
That would stop the
release of the non-functional postgresql on hurd-i386, no?
Friedrich
>
Hi
It seems to me that the test for Postgresql in configure is not correct.
I think it is testing if Postgresql is installed in the host environment
instead of the target environment.
Have fun
___
pspp-dev mailing list
[email protected]
https
On Fri, Mar 18, 2016 at 08:53:09PM +0100, Harry Thijssen wrote:
Hi
It seems to me that the test for Postgresql in configure is not correct.
I think it is testing if Postgresql is installed in the host environment
instead of the target environment.
There are
14 matches
Mail list logo
