Am 2006-07-06 19:25:38, schrieb Ron Johnson:
SQL was used 20 years ago, why not 20 years from now?
I can't see needing data from 10 years ago, but you never know.
I have a Database (currently around 370 GByte of historical data,
exactly the last 14600 years, but most from the last 100 years)
On 07/12/2006 09:25:45 AM, Jan Wieck wrote:
On 7/6/2006 8:03 PM, Karl O. Pinc wrote:
On 07/06/2006 06:14:39 PM, Florian G. Pflug wrote:
Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored
On 7/6/2006 8:03 PM, Karl O. Pinc wrote:
On 07/06/2006 06:14:39 PM, Florian G. Pflug wrote:
Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored into a future PostgreSQL
cluster.
Anyway, 20
I think that that's the answer, put the whole OS and db on a
bootable cd or DVD. In 20 years they'll surely be no
problem running the whole thing from RAM so media access
speed should not be an issue.
You are correct. I thought that CD only had a shelf life of 5 to 10 years.
This is true
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karl O. Pinc wrote:
On 07/12/2006 09:25:45 AM, Jan Wieck wrote:
On 7/6/2006 8:03 PM, Karl O. Pinc wrote:
On 07/06/2006 06:14:39 PM, Florian G. Pflug wrote:
Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
hardware.
Jan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jan Wieck
Sent: Wednesday, July 12, 2006 9:26 AM
To: Karl O. Pinc
Cc: Florian G. Pflug; pgsql-general@postgresql.org; [EMAIL PROTECTED]
Subject: Re: [GENERAL] Long term database archival
On Wednesday 12 July 2006 08:37, Richard Broersma Jr wrote:
I think that that's the answer, put the whole OS and db on a
bootable cd or DVD. In 20 years they'll surely be no
problem running the whole thing from RAM so media access
speed should not be an issue.
You are correct. I
To: Karl O. Pinc
Cc: Florian G. Pflug; pgsql-general@postgresql.org; [EMAIL PROTECTED]
Subject: Re: [GENERAL] Long term database archival
On 7/6/2006 8:03 PM, Karl O. Pinc wrote:
On 07/06/2006 06:14:39 PM, Florian G. Pflug wrote:
Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long
Jan Wieck [EMAIL PROTECTED] writes:
I can't even find the same hardware I bought last year. That's one of the
reasons why I use VMware on my laptop. It has a hardware abstraction layer
that
presents default XVGA and Soundblaster cards etc. to the guest OS. When I buy
a
new laptop, I just
-- Forwarded message --
From: Marco Bizzarri [EMAIL PROTECTED]
Date: Jul 12, 2006 9:03 PM
Subject: Re: [GENERAL] Long term database archival
To: Karl O. Pinc [EMAIL PROTECTED]
Long term archival of electronic data is a BIG problem in the
archivist community. I remember, a few
On Wednesday 12. July 2006 21:03, Marco Bizzarri wrote:
Long term archival of electronic data is a BIG problem in the
archivist community. I remember, a few years ago, a paper describing
the problem of historical (20+ years old) data which were running the
risk of being lost simply because of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Hart wrote:
Wouldn't you run into driver problems if you tried to restore a
20 year old image? After all, you probably won't be using the
same hardware in 20 years...
Scarily, the current PC architecture is just a set of add-ons and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leif B. Kristensen wrote:
On Wednesday 12. July 2006 21:03, Marco Bizzarri wrote:
Long term archival of electronic data is a BIG problem in the
archivist community. I remember, a few years ago, a paper
describing the problem of historical (20+
On Fri, Jul 07, 2006 at 09:09:22AM -0700, Richard Broersma Jr wrote:
I think that in twenty years, I think most of us will be more worried about
our retirement than
the long terms data conserns of the companies we will no longer be working
for. :-D
You may want to take precautions now such
On Thu, 6 Jul 2006, Dann Corbit wrote:
It's the data that contains all the value. The hardware becomes
obsolete when it can no longer keep up with business needs.
. or can no longer be repaired. :)
---(end of broadcast)---
TIP 5: don't
On Thu, 2006-07-06 at 20:57, Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored into a future PostgreSQL
cluster.
Should we want to restore a 20 year old backup
nobody's going to want to
On 7/7/2006 17:49, Csaba Nagy [EMAIL PROTECTED] wrote:
On Thu, 2006-07-06 at 20:57, Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored into a future PostgreSQL
cluster.
Should we want
Csaba Nagy schrieb:
...
Karl, I would say that if you really want data from 20 years ago, keep
it in the custom format, along with a set of the sources of postgres
which created the dump. then in 20 years when you'll need it, you'll
compile the sources and load the data in the original postgres
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ben wrote:
On Thu, 6 Jul 2006, Dann Corbit wrote:
It's the data that contains all the value. The hardware becomes
obsolete when it can no longer keep up with business needs.
. or can no longer be repaired. :)
of course you might need to also keep an image of the current
OS and the hardware you're running on if you really want to be sure it
will work in 20 years :-)
I think that in twenty years, I think most of us will be more worried about our
retirement than
the long terms data conserns of the
On Jul 7, 2006, at 1:19 AM, Csaba Nagy wrote:
On Thu, 2006-07-06 at 20:57, Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored into a future PostgreSQL
cluster.
Should we want to restore a
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored into a future PostgreSQL
cluster.
Mostly, we're interested in dumps done with
--data-only, and have preferred the
default (-F c) format. But this form is somewhat
Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored into a future PostgreSQL
cluster.
Mostly, we're interested in dumps done with
--data-only, and have preferred the
default (-F c) format. But
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian G. Pflug wrote:
Karl O. Pinc wrote:
[snip]
Anyway, 20 years is a _long_, _long_ time. If you _really_ need
to keep your data that long, I'd suggest you create text-only
schema dumps, and text-only data dumps. The postgres developers
are
Will postgresql be a viable database in 20 years? Will SQL be used
anywhere in 20 years? Are you sure 20 years is your ideal backup
duration?
Very few media even last 5 years. The good thing about open source and
open standards is that regardless of the answers to those questions,
there is
On 07/06/2006 06:14:39 PM, Florian G. Pflug wrote:
Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored into a future PostgreSQL
cluster.
Anyway, 20 years is a _long_, _long_ time.
Yes, but
Will postgresql be a viable database in 20 years? Will SQL be used
anywhere in 20 years? Are you sure 20 years is your ideal backup
duration?
Very few media even last 5 years. The good thing about open source and
open standards is that regardless of the answers to those questions,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Agent M wrote:
Will postgresql be a viable database in 20 years? Will SQL be used
anywhere in 20 years? Are you sure 20 years is your ideal backup duration?
SQL was used 20 years ago, why not 20 years from now?
I can't see needing data from 10
I am not to sure of the relevance, but I periodically worked as a
sub-contractor for an
Oil-producing Company in California. They were carrying 35 years of
data on an Alpha Server
running Ca-Ingres. The really bad part is that hundreds and hundreds
of reporting tables were
created on top of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Broersma Jr wrote:
[snip]
I am not to sure of the relevance, but I periodically worked as a
sub-contractor for an Oil-producing Company in California. They
were carrying 35 years of data on an Alpha Server running
Ca-Ingres. The
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Agent M wrote:
[snip]
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.
Ingres has been around for longer than you think: about
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-general-
[EMAIL PROTECTED] On Behalf Of Ron Johnson
Sent: Thursday, July 06, 2006 5:26 PM
To: Postgres general mailing list
Subject: Re: [GENERAL] Long term database archival
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dann Corbit wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-general-
[EMAIL PROTECTED] On Behalf Of Ron Johnson
Sent: Thursday, July 06, 2006 5:26 PM
To: Postgres general mailing list
Subject: Re: [GENERAL] Long term
34 matches
Mail list logo
