Auditing PostgreSQL Databases Using Logical Decoding
Formal Metadata
| Title | Auditing PostgreSQL Databases Using Logical Decoding |
|
| Title of Series | |
| Part Number | 13 |
| Number of Parts | 193 |
| Author | |
| License | CC Attribution 3.0 Germany: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Have you ever been wondering what edits are happening inside your databases?
Logcial Decoding, introduced in PostgreSQL 9.4, allows to keep track of
changes commited to the database. This talk presents how this mechanism can be used to audit PostGIS/PostgreSQL databases. After an introduction to the concepts of logical decoding,
two use cases are presented:
Quality Assurance: writing an audit log into the database after each commit so that someone else can do a review of the modified data.
Cache Invalildation: refreshing a GeoWebCache instance at the regions in which the data has
changed after each commit.
To support these two use cases, a little Java program able to be run as a mircoservice was developed and will be shared under an open source license with the community via github. |
|