Magnus Hagander wrote:
Looking around the lc_messages stuff a bit, I notice it's set to
superuser-only.
I do use
ALTER USER joe SET lc_messages='sv_SE'
now and then to change the language for a user. And I see it's also
possible to use it on a database level by doing
ALTER DATABASE
Magnus Hagander [EMAIL PROTECTED] writes:
Is there a reason for this?
Two arguments I can recall:
(1) Having log messages emitted in a language that the DBA can't read
would be a useful tactic for a Bad Guy trying to cover his tracks.
(2) Setting lc_messages to a value incompatible with the
It is so that the user cannot hide log messages he causes by setting the
language to something that the administrator cannot understand. (There are
more conceivable scenarios of that sort, such as exploiting the
administrator's ad hoc log parsing tool.)
--
Peter Eisentraut
On Mon, Jul 23, 2007 at 11:20:15AM -0400, Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
Is there a reason for this?
Two arguments I can recall:
(1) Having log messages emitted in a language that the DBA can't read
would be a useful tactic for a Bad Guy trying to cover his
