ALTER USER ..... PASSWORD ....

From: Rafal Pietrak <rafal(at)zorro(dot)isa-geek(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: ALTER USER ..... PASSWORD ....
Date: 2006-06-06 08:07:46
Message-ID: 1149581267.6752.28.camel@model.home.waw.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Just wondering,

psql clinet tool loggs issued commands into ~/.psql_history, which is
VERY usefull. I exercise grep-ing the file extensively.

But when it comes to command like "ALTER/CREATE USER ... PASSWORD" I'd
rather have it NOT logged.

This is not a major issue, since there are workarounds - temporary
switching the logging off, etc. Still one have to keep thinking of that
and I have forgot occasionally, still there might be admins which don't
really care.

The implementation should be fairly simple for psql author (I guess :),
but I myself am not up to knowing if it really is. The problem looks
simple: psql-tool should filter away 'sensitive' sql-commands, before
putting them into the log? But the implementation is not so trivial,
since it should take into account not filtering: "ALTER TABLE 'user' add
column password text" and other such similarities, which should actually
be logged.

Comments?

--
-R

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2006-06-06 08:58:26 How to use index in case insensitive substing search
Previous Message Brian Mathis 2006-06-06 05:30:25 Problem with postgresql-docs-8.1.4-1PGDG.i686.rpm