# Auditing Changes with Hstore

DevFeed: [Auditing Changes with Hstore](<https://devfeed.tech/articles/auditing-changes-with-hstore-34512.md>)

Original publisher: [Read original article](<https://tapoueh.org/blog/2013/08/auditing-changes-with-hstore/>)

Author: Dimitri Fontaine PostgreSQL Major Contributor; Author

Published: 2013-08-27T15:35:00Z

Content type: tutorial

Language: en

Sources: [Dimitri Fontaine](<https://devfeed.tech/sources/dimitri-fontaine.md>)

Topics: [data](<https://devfeed.tech/topics/data.md>)

Tags: [article](<https://devfeed.tech/tags/article.md>), [changes](<https://devfeed.tech/tags/changes.md>), [pl-pgsql](<https://devfeed.tech/tags/pl-pgsql.md>)

## AI overview

This tutorial explains how to use PostgreSQL's hstore extension with a trigger to audit row changes. It stores full hstore representations of the data before and after updates, preserving enough history to reconstruct a row's value over time.

## Source excerpt

In a previous article about Trigger Parameters we have been using the extension hstore in order to compute some extra field in our records, where the fields used both for the computation and for storing the results were passed in as dynamic parameters. Today we're going to see another trigger use case for hstore: we are going to record changes made to our tuples.