| From: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
|---|---|
| To: | Agent M <agentm(at)themactionfaction(dot)com>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Long term database archival |
| Date: | 2006-07-07 01:07:17 |
| Message-ID: | 20060707010717.43773.qmail@web31807.mail.mud.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> But the data from 35 years ago wasn't stored in Ingres and, if it's
> important, it won't stay in Ingres. The data shifts from format to
> format as technology progresses.
>
> It seemed to me that the OP wanted some format that would be readable
> in 20 years. No one can guarantee anything like that.
What you are saying could be true, but that wasn't what I was lead to believe. This Database was
logging data from the production automation system. I believe the need for 30+ years of data was
because the client was interested in determining / trending the gradual drop off in production
over the year.
Their interest is in extrapolating profitability lifetime for their facility. Essentially want to
know how long they have before they have to "close the doors."
But you are probably correct, I had no way of really knowing how old that data on there server
really was.
Regards,
Richard Broersma Jr.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2006-07-07 01:16:24 | Re: Long term database archival |
| Previous Message | Richard Broersma Jr | 2006-07-07 00:59:12 | Re: Old data (was Re: Long term database archival) |