Re: pgsql: Add pg_audit, an auditing extension - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Add pg_audit, an auditing extension
Date
Msg-id 21368.1431618712@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Add pg_audit, an auditing extension  (Stephen Frost <sfrost@snowman.net>)
Responses Re: pgsql: Add pg_audit, an auditing extension  (Stephen Frost <sfrost@snowman.net>)
List pgsql-committers
Stephen Frost <sfrost@snowman.net> writes:
> I've pushed a change which should clean it up by simply loading the
> module after each reconnects is done, more-or-less simulating having it
> be in shared_preload_libraries.  It also wasn't using the correct
> database for reconnecting.

> I'll keep an eye on it.

Another thing that looks not amazingly well-thought-out about that
regression test is that it creates a superuser role with a known name
(and no password, not that adding a password would make it better).
This seems like it's just asking for trouble, especially in installcheck
scenarios where failure partway through would leave the superuser lying
around ready to be exploited.  Do we *really* need that in the test?

            regards, tom lane


pgsql-committers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: pgsql: Add pg_audit, an auditing extension
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Further fixes for the buildfarm for pg_audit