On Fri, Apr 3, 2015 at 10:01 PM, David Steele <da...@pgmasters.net> wrote: > On 4/3/15 3:59 AM, Sawada Masahiko wrote: >> On Thu, Apr 2, 2015 at 2:46 AM, David Steele <da...@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.gl3...@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.gl3...@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. >
I tested v6 patch, but I got SEGV when I executed test() function I mentioned up thread. Could you address this problem? Regards, ------- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
