From: Craig James <craig_james@emolecules.com>
To: Lukasz Brodziak <lukasz.brodziak@hotmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: Tuple changes from relfilenodes
Date: Fri, 27 Aug 2010 10:27:13 -0700
Message-ID: <4C77F571.40505@emolecules.com> (raw)
In-Reply-To: <SNT125-W56AEE871B4070B93CF9BBF9860@phx.gbl>
References: <SNT125-W2321CA0976D766C95D975DF9860@phx.gbl>
<4C7776760200002500034D06@gw.wicourts.gov>
<SNT125-W9E0FB58245FF91EE836BAF9860@phx.gbl>
<4C77F027.7040508@emolecules.com>
<SNT125-W56AEE871B4070B93CF9BBF9860@phx.gbl>
On 8/27/10 10:09 AM, Lukasz Brodziak wrote:
> What do You mean by history table? Creating such table is out of the question.
You asked for "actual versions of row data" and a "data change history." How can you expect to get a history without the history being stored somewhere? The previous answers to your question already said that the old versions of data can be erased almost immediately, so if you really need the history, you have to do it yourself.
Why is that out of the question? Perhaps a more detailed explanation of what you are trying to achieve would help.
Craig
>
> > Date: Fri, 27 Aug 2010 10:04:39 -0700
> > From: craig_james@emolecules.com
> > To:
> > Subject: Re: [ADMIN] Tuple changes from relfilenodes
> >
> > On 8/27/10 9:48 AM, ?ukasz Brodziak wrote:
> > > I'm looking for actual versions of row data. What I want to achieve as a final result is a kind of data change history.
> >
> > What about a before-update trigger and an history table?
> >
> > Craig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: craig_james@emolecules.com, lukasz.brodziak@hotmail.com
Subject: Re: Tuple changes from relfilenodes
In-Reply-To: <4C77F571.40505@emolecules.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox