Обсуждение: [ADMIN] Issue related to audit trigger after upgrade to Postgresql9.6
Hi,
We have upgraded database from 9.2 to 9.6. https://wiki.postgresql.org/wiki/Audit_trigger_91plus
Our applications depend on this transaction_id which is misbehaving currently.
How we can handle this situation.
Thanks in advance.
Regards
Vikash Kumar Pandey.
Hi,
Does anyone has any idea?On Mon, Jan 2, 2017 at 1:25 PM, Vikash Pandey <vikash.kumar.pandey@gmail.com> wrote:
After upgradation this transaction_id some how reset itself which was unexpected.In this trigger function there is transaction_id which is generated by txid_current()In 9.2 we were using auditing of tables through audit trigger.Hi,We have upgraded database from 9.2 to 9.6.
https://wiki.postgresql.org/wiki/Audit_trigger_91plus Our applications depend on this transaction_id which is misbehaving currently.How we can handle this situation.Thanks in advance.RegardsVikash Kumar Pandey.
Have you tried to create an issue on this github project ?
Maybe this solution was abandoned and you should take a look on a new auditory solution like: https://github.com/pgaudit/pgaudit
2017-01-19 14:24 GMT+01:00 Vikash Pandey <vikash.kumar.pandey@gmail.com>:
Vikash Kumar PandeyRegardsWe are stuck.Hi,Does anyone has any idea?On Mon, Jan 2, 2017 at 1:25 PM, Vikash Pandey <vikash.kumar.pandey@gmail.com> wrote: After upgradation this transaction_id some how reset itself which was unexpected.In this trigger function there is transaction_id which is generated by txid_current()In 9.2 we were using auditing of tables through audit trigger.Hi,We have upgraded database from 9.2 to 9.6.
https://wiki.postgresql.org/wiki/Audit_trigger_91plus Our applications depend on this transaction_id which is misbehaving currently.How we can handle this situation.Thanks in advance.RegardsVikash Kumar Pandey.