On 12/22/2013 05:21 PM, Thom Brown wrote:
> On 23 December 2013 01:15, Thom Brown <thom@linux.com> wrote:
>> On 23 December 2013 01:13, Adrian Klaver <adrian.klaver@gmail.com> 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/Development/psql/bin//psql
>> /home/thom/Development/psql/bin//pgbench
>
> 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:
>
> thom@swift ~/Development $ which psql pgbench
> /home/thom/Development/psql/bin/psql
> /home/thom/Development/psql/bin/pgbench
> thom@swift ~/Development $ psql postgres
> psql (9.4devel)
> Type "help" for help.
>
> postgres=# \q
> thom@swift ~/Development $ pgbench -i -s 20 pgbench
> NOTICE: table "pgbench_history" does not exist, skipping
> NOTICE: table "pgbench_tellers" does not exist, skipping
> NOTICE: table "pgbench_accounts" does not exist, skipping
> NOTICE: table "pgbench_branches" does not exist, skipping
> creating tables...
> 100000 of 2000000 tuples (5%) done (elapsed 0.10 s, remaining 1.86 s).
> 200000 of 2000000 tuples (10%) done (elapsed 0.19 s, remaining 1.72 s).
> ...
>
> So it's all working now, but I don't know why. I don't think that
> change would be the thing that fixed it. Perhaps it's something to do
> with me attempting to run pgbench before building the development
> contrib module of it, so it picks up the OS package-installed version,
> and when I go to build the local dev version, it has cached the
> location for the domain socket from the previous attempt. *shrug*
That's what I like, problems that fix themselves:)
>
--
Adrian Klaver
adrian.klaver@gmail.com
