Re: SV: Implementing pgaudit extension on Microsoft Windows

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Niels Jespersen <NJN(at)dst(dot)dk>
Cc: "'Pavel Stehule'" <pavel(dot)stehule(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: SV: Implementing pgaudit extension on Microsoft Windows
Date: 2019-02-12 14:14:06
Message-ID: 30167.1549980846@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Niels Jespersen <NJN(at)dst(dot)dk> writes:
> Same result from
> pgaudit.log = 'all'
> in postgresql.conf and after both select pg_reload_conf(); and after service restart.
> No entries in the log from audit.

Hm. I don't know much about pgaudit, but just from scanning its
documentation, it doesn't seem like there's anything else that
has to be set.

I wonder whether pgaudit actually works on Windows? It might have
some weird dependency on children being spawned with fork not exec,
for instance. You probably ought to contact the authors and ask.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Fink (PDF) 2019-02-12 14:52:09 BDR 1.0: background worker wants to start that should not be there
Previous Message Rich Shepard 2019-02-12 13:42:56 Re: Blank, nullable date column rejected by psql