From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Add pg_audit, an auditing extension |
Date: | 2015-05-14 15:51:52 |
Message-ID: | 21368.1431618712@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-05-14 15:53:23 | Re: pgsql: Further fixes for the buildfarm for pg_audit |
Previous Message | Stephen Frost | 2015-05-14 15:46:19 | Re: pgsql: Add pg_audit, an auditing extension |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-05-14 15:59:42 | Re: trust authentication behavior |
Previous Message | Stephen Frost | 2015-05-14 15:46:19 | Re: pgsql: Add pg_audit, an auditing extension |