On 12/22/2013 5:21 PM, Thom Brown wrote:
Hmm... now this is odd. I went to correct the PATH information in my
.bashrc script file (to remove the superfluous trailing
forward-slash), and when running both psql and pgbench in a new
terminal, all is fine:
fyi, I was going to suggest ther'es more
On 12/22/2013 05:21 PM, Thom Brown wrote:
On 23 December 2013 01:15, Thom Brown wrote:
On 23 December 2013 01:13, Adrian Klaver wrote:
On 12/22/2013 04:51 PM, Thom Brown wrote:
I should have mentioned that I've checked that:
thom@swift ~/Development $ which psql pgbench
/home/thom/Develop
On 23 December 2013 01:15, Thom Brown wrote:
> On 23 December 2013 01:13, Adrian Klaver wrote:
>> On 12/22/2013 04:51 PM, Thom Brown wrote:
>>
>>> PostgreSQL using unix domain sockets by not specifying any host with
>>> psql, and the same applies to vacuumdb, createdb and dropdb. However,
>>> wh
On 23 December 2013 01:13, Adrian Klaver wrote:
> On 12/22/2013 04:51 PM, Thom Brown wrote:
>
>> PostgreSQL using unix domain sockets by not specifying any host with
>> psql, and the same applies to vacuumdb, createdb and dropdb. However,
>> when I go to use pgbench, it seems to be looking in the
On 12/22/2013 04:51 PM, Thom Brown wrote:
PostgreSQL using unix domain sockets by not specifying any host with
psql, and the same applies to vacuumdb, createdb and dropdb. However,
when I go to use pgbench, it seems to be looking in the wrong place
for the domain socket:
thom@swift ~/Developme
Hi all,
I'm a bit confused by my development set up. I can connect to
PostgreSQL using unix domain sockets by not specifying any host with
psql, and the same applies to vacuumdb, createdb and dropdb. However,
when I go to use pgbench, it seems to be looking in the wrong place
for the domain sock
