The following bug has been logged online:

Bug reference: 2840
Logged by: Ned T. Crigler
Email address: crigler@users.sourceforge.net
PostgreSQL version: 8.2
Operating system: Linux (Debian unstable)
Description: \set HISTCONTROL ignoredups doesn't work in psql
Details:

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.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

On 12/19/06, Ned T. Crigler <crigler@users.sourceforge.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[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | yahoo }.com

"Ned T. Crigler" <crigler@users.sourceforge.net> writes:
> Description: \set HISTCONTROL ignoredups doesn't work in psql

Ooops, seems it got broken somewhere between 8.1 and 8.2. Thanks for
the report!

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

"Ned T. Crigler" <crigler@users.sourceforge.net> writes:
> Description: \set HISTCONTROL ignoredups doesn't work in psql

Fixed, thanks for the report.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly