SV: SV: Implementing pgaudit extension on Microsoft Windows
От | Niels Jespersen |
---|---|
Тема | SV: SV: Implementing pgaudit extension on Microsoft Windows |
Дата | |
Msg-id | 3967181ED595B445B1E39718204FD4BD0107BC9BC8@SRVEXC5.dst.local обсуждение исходный текст |
Ответ на | Re: SV: Implementing pgaudit extension on Microsoft Windows (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: SV: SV: Implementing pgaudit extension on Microsoft Windows
|
Список | pgsql-general |
Hi Tom (and others) Thank you for input. I think my next steps will be approcching the problem from differenct angles: Implement on Linux as Proof of Concept. Dive into the source for pgaudit and try to understand how it works, perhaps getting a small example extension working alongthe way. Perhaps contacting the authors of pgaudit to have them confirm that there exists working implementations of pgaudit on Windows(and if so if they are on PostgreSQL 11). I will report how this turns out. Regards Niels -----Oprindelig meddelelse----- Fra: Tom Lane <tgl@sss.pgh.pa.us> Sendt: 12. februar 2019 15:14 Til: Niels Jespersen <NJN@dst.dk> Cc: 'Pavel Stehule' <pavel.stehule@gmail.com>; pgsql-general@lists.postgresql.org Emne: Re: SV: Implementing pgaudit extension on Microsoft Windows Niels Jespersen <NJN@dst.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 elsethat has to be set. I wonder whether pgaudit actually works on Windows? It might have some weird dependency on children being spawned with forknot exec, for instance. You probably ought to contact the authors and ask. regards, tom lane
В списке pgsql-general по дате отправления: