Re: Auditing extension for PostgreSQL (Take 2) - Mailing list pgsql-hackers

From David Steele
Subject Re: Auditing extension for PostgreSQL (Take 2)
Date
Msg-id 551E8F37.2060202@pgmasters.net
Whole thread Raw
In response to Re: Auditing extension for PostgreSQL (Take 2)  (Sawada Masahiko <sawada.mshk@gmail.com>)
Responses Re: Auditing extension for PostgreSQL (Take 2)
Re: Auditing extension for PostgreSQL (Take 2)
List pgsql-hackers
On 4/3/15 3:59 AM, Sawada Masahiko wrote:
> On Thu, Apr 2, 2015 at 2:46 AM, David Steele <david@pgmasters.net> wrote:
>> Let me know if you see any other issues.
>>
>
> I pulled HEAD, and then tried to compile source code after applied
> following "deparsing utility command patch" without #0001 and #0002.
> (because these two patches are already pushed)
> <http://www.postgresql.org/message-id/20150325175954.GL3636@alvh.no-ip.org>
>
> But I could not use new pg_audit patch due to compile error (that
> deparsing utility command patch might have).
> I think I'm missing something, but I'm not sure.
> Could you tell me which patch should I apply before compiling pg_audit?

When Alvaro posted his last patch set he recommended applying them to
b3196e65:

http://www.postgresql.org/message-id/20150325175954.GL3636@alvh.no-ip.org

Applying the 3/25 deparse patches onto b3196e65 (you'll see one trailing
space error) then applying pg_audit-v6.patch works fine.

--
- David Steele
david@pgmasters.net


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: The return value of allocate_recordbuf()
Next
From: Robert Haas
Date:
Subject: Re: Abbreviated keys for Numeric