Thanks for the fix, it also fixed the problem here (also on Debian).
On Sun, Jan 20, 2019 at 11:51:20AM +0100, John Darrington wrote:
> I pushed a fix which seems to solve the problem at least on debian ...
>
> J'
>
> On Sun, Jan 20, 2019 at 09:00:59AM +0100, John Darrington wrote:
> I had
I pushed a fix which seems to solve the problem at least on debian ...
J'
On Sun, Jan 20, 2019 at 09:00:59AM +0100, John Darrington wrote:
I had a look at this, and spoke to some of the postgres people.
It seems that postgres is not after all the guilty party. Debian is.
I had a look at this, and spoke to some of the postgres people.
It seems that postgres is not after all the guilty party. Debian is.
Debian's /usr/bin/psql is a wrapper around the real psql which breaks
things.
I'll see what the best way around this problem is.
J'
On Sat, Jan 19, 2019 at 08:
I'm getting the same results.
So I suspect the test needs to be adjusted to suit recent psqlserver
versions.
J'
On Sat, Jan 19, 2019 at 09:16:09AM -0800, Ben Pfaff wrote:
I've recently had to move development to a new laptop because my
previous one died suddenly. I'm getting the foll
I'm pretty sure that this test is trying to create a database server of
its own rather than using the system's server. It worked for me OK
before without any special configuration, but it is not working with my
new laptop.
I think that John wrote this test, so perhaps he will have some
thoughts.
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 create your "blp"
