The point is, it hangs around: in backup 'tapes' to begin with.
And if it's the case of postmaster history, there may be lots of other
people passwords to find. (So I generaly disable postmaster
psql_history, but that's a nuicence).
But as I said, it's a sort of a nuicence, not really an issue.
Rafal Pietrak <[EMAIL PROTECTED]> writes:
> 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.
The history file is onl
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 -
