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:
