Re: BUG #2840: \set HISTCONTROL ignoredups doesn't work in psql

From: "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com>
To: "Ned T(dot) Crigler" <crigler(at)users(dot)sourceforge(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2840: \set HISTCONTROL ignoredups doesn't work in psql
Date: 2006-12-19 15:59:16
Message-ID: 65937bea0612190759s144ea081id9fa394de6f42fc8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 12/19/06, Ned T. Crigler <crigler(at)users(dot)sourceforge(dot)net> wrote:
>
>
> In psql, doing:
>
> \set HISTCONTROL ignoredups
> select 1;
> select 1;
> select 1;
> select 1;
> select 1;
>
> adds every select statement into the history, instead of ignoring the
> duplicate statements.
>

Can you please let us know the environment? If it is psql on Windows, then I
think it is the cmd.exe thats storing that history for you and not psql
itself.

Regards,

--
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | yahoo }.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-12-19 16:14:27 Re: BUG #2840: \set HISTCONTROL ignoredups doesn't work in psql
Previous Message Tom Lane 2006-12-19 15:58:48 Re: No error when FROM is missing in subquery