Re: pgaudit - an auditing extension for PostgreSQL - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgaudit - an auditing extension for PostgreSQL
Date
Msg-id 16906.1403539164@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgaudit - an auditing extension for PostgreSQL  (Stephen Frost <sfrost@snowman.net>)
Responses Re: pgaudit - an auditing extension for PostgreSQL  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> I'd expect a catalog table or perhaps changes to pg_class (maybe other
> things also..) to define what gets logged.

How exactly will that work for log messages generated in contexts where
we do not have working catalog access?  (postmaster, crash recovery,
or pretty much anywhere where we're not in a valid transaction.)

This strikes me as much like the periodic suggestions we hear to get
rid of the GUC infrastructure in favor of keeping all those settings
in a table.  It doesn't work because too much of that info is needed
below the level of working table access.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: /proc/self/oom_adj is deprecated in newer Linux kernels
Next
From: Kevin Grittner
Date:
Subject: Re: [HACKERS] please review source(SQLServer compatible)‏