Sumanth Vishwaraj <sumanth.vishwaraj@oracle.com> writes:
> We would like PostgreSQL to store the details of who made the change (user/session) information in the transaction
log.
You can build that yourself, typically by adding a trigger that stores
the value of "current_user" into inserted/updated rows. (If you want
to also track deletions, a separate audit log table would work
better.) The event-trigger feature might also be useful.
It's unlikely that we'd consider implementing such functionality at a
lower level, because these sorts of requirements always come with an
array of application-specific details about what is to be logged.
It would be impractical to satisfy all such cases in one implementation.
There would also be concerns about imposing overhead on users who
have no need for such a feature.
regards, tom lane
