| From: | Rodrigo De León <rdeleonp(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Historical Data Question |
| Date: | 2007-06-14 20:53:26 |
| Message-ID: | 1181854406.805516.187080@q19g2000prn.googlegroups.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jun 14, 12:57 pm, Lza <dayw(dot)(dot)(dot)(at)gmail(dot)com> wrote:
> Can anyone help me with this problem?
>
> I have a table in my database that holds information on policies and
> this table is linked to a number of other tables. I need to be able to
> keep a history of all changes to a policy over time. The other tables
> that are linked to policy also need to store historical data. When I
> run a query on the policy table for a certain period, I also need to
> be able to pull the correct related rows (i.e. the information that
> would have been in the table at that time) from the tables linked to
> it.
>
> Does anyone have any suggestions on how to store historical
> information in databases? Any good resources (books, etc..) that cover
> this information?
>
> Thanks for your time.
See: http://www.postgresql.org/docs/8.2/static/plpgsql-trigger.html
Search for: "Example 37-3. A PL/pgSQL Trigger Procedure For Auditing"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-14 20:55:11 | Re: Hash Aggregate plan picked for very large table == out of memory |
| Previous Message | Tom Lane | 2007-06-14 20:43:10 | Re: pg_restore out of memory |