Skip site navigation (1) Skip section navigation (2)

Re: revised hstore patch

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: revised hstore patch
Date: 2009-07-22 01:10:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

Andrew Gierth wrote:
> The code already has users who are using it for audit-trail stuff
> (easily computing the changes between old and new records and storing
> only the differences). Perhaps one of the existing users could express
> an opinion on this point.
I use it for exactly that purpose (and it works extremely well). I'm not 
sure we have any values > 64k, though, and certainly our keys are tiny - 
they are all column names. OTOH, that could well be an annoying 
limitation, and would be easily breached if the changed field were some 
binary object like an image or a PDF.

I rather like your idea of doing a convert-on-write, if you can reliably 
detect that the data is in the old or new format.



In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-07-22 01:21:22
Subject: pgsql: Tweak TOAST code so that columns marked with MAIN storage
Previous:From: Itagaki TakahiroDate: 2009-07-22 01:09:17
Subject: Re: Duplicate key value error

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group