search

EndPointCorp / end-point-blog

End Point Dev blog
https://www.endpointdev.com/blog/
17 stars 65 forks source link

Comments for Protecting and auditing your secure PostgreSQL data #548

Open phinjensen opened 6 years ago

phinjensen commented 6 years ago

Comments for https://www.endpointdev.com/blog/2012/01/protecting-auditing-postgresql-data/ By Greg Sabino Mullane

To enter a comment:

  1. Log in to GitHub
  2. Leave a comment on this issue.
phinjensen commented 6 years ago 
original author: simon@2ndQuadrant.com
date: 2012-02-01T05:54:22-05:00

Good post. I'm hoping to work on Autonomous Transactions for PostgreSQL 9.3, which will allow auditing transactions to happen even if the main transaction rolls back.

phinjensen commented 6 years ago 
original author: Jon Jensen
date: 2012-02-01T13:11:15-05:00

Simon, that would be an excellent feature to have! I look forward to testing. :)

phinjensen commented 6 years ago 
original author: Raghavendra
date: 2012-09-29T09:44:21-04:00

Autonomous Transaction !!!

+1

Looking forward to it. By the way great post about auditing.

One question, any overhead by enabling auditing at row level ?

--Raghav

phinjensen commented 6 years ago 
original author: Greg Sabino Mullane
date: 2012-10-04T14:29:48-04:00

Raghav: yes, there is an overhead to all trigger functions, and this one in particular is probably a little heavier than most due to its need to perform those out-of-band database interactions. As with everything thought, the only way to know how much overhead is to measure!