From: | Jaime Soler <jaime(dot)soler(at)gmail(dot)com> |
---|---|
To: | Vikash Pandey <vikash(dot)kumar(dot)pandey(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Issue related to audit trigger after upgrade to Postgresql9.6 |
Date: | 2017-02-22 16:45:16 |
Message-ID: | CAKVUGgR7F_r-MbXwZbzhquQ+CVP+4LuTXqz1ukwWX1oiANsgNg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(dot)kumar(dot)pandey(at)gmail(dot)com>:
> Hi,
>
> Does anyone has any idea?
> We are stuck.
>
> Regards
> Vikash Kumar Pandey
>
>
> On Mon, Jan 2, 2017 at 1:25 PM, Vikash Pandey <
> vikash(dot)kumar(dot)pandey(at)gmail(dot)com> wrote:
>
>> Hi,
>>
>> We have upgraded database from 9.2 to 9.6.
>> In 9.2 we were using auditing of tables through audit trigger.
>> https://wiki.postgresql.org/wiki/Audit_trigger_91plus
>>
>> In this trigger function there is transaction_id which is generated by
>> txid_current()
>> After upgradation this transaction_id some how reset itself which was
>> unexpected.
>> Our applications depend on this transaction_id which is misbehaving
>> currently.
>> How we can handle this situation.
>>
>>
>> Thanks in advance.
>>
>>
>> Regards
>> Vikash Kumar Pandey.
>>
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Emery | 2017-02-22 18:45:09 | Database vs Schema Separation |
Previous Message | Jaime Soler | 2017-02-22 14:33:59 | Re: PGSQL as database server container |