Re: Auditing extension for PostgreSQL (Take 2)

From: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>
To: David Steele <david(at)pgmasters(dot)net>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Subject: Re: Auditing extension for PostgreSQL (Take 2)
Date: 2015-04-30 03:57:19
Message-ID: CAD21AoCQSGZ5x+sfs4g1x_8Fip60x8ULQFTAGB5XTrKQZvPWPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 29, 2015 at 12:17 AM, David Steele <david(at)pgmasters(dot)net> wrote:
> On 4/28/15 2:14 AM, Sawada Masahiko wrote:
>> On Fri, Apr 24, 2015 at 3:23 AM, David Steele <david(at)pgmasters(dot)net> wrote:
>>> I've also added some checking to make sure that if anything looks funny
>>> on the stack an error will be generated.
>>>
>>> Thanks for the feedback!
>>>
>>
>> Thank you for updating the patch!
>> I ran the postgres regression test on database which is enabled
>> pg_audit, it works fine.
>> Looks good to me.
>>
>> If someone don't have review comment or bug report, I will mark this
>> as "Ready for Committer".
>
> Thank you! I appreciate all your work reviewing this patch and of
> course everyone else who commented on, reviewed or tested the patch
> along the way.
>

I have changed the status this to "Ready for Committer".

Regards,

-------
Sawada Masahiko

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2015-04-30 04:31:31 Re: Reducing tuple overhead
Previous Message Sawada Masahiko 2015-04-30 03:54:49 Re: Proposal: knowing detail of config files via SQL