From: Gnanakumar <gnanam@zoniac.com>
To: 'Craig James' <cjames@emolecules.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Database archive solutions
Date: Thu, 22 Nov 2012 11:33:19 +0530
Message-ID: <00de01cdc877$15dcfcc0$4196f640$@zoniac.com> (raw)
In-Reply-To: <CAFwQ8rfvoNtqCwsW267RTfhGEchGZGpme9jc4Xbv-kevU0FoHQ@mail.gmail.com>
References: <014101cdc7c9$a73bcb00$f5b36100$@zoniac.com>
<CAFwQ8rfvoNtqCwsW267RTfhGEchGZGpme9jc4Xbv-kevU0FoHQ@mail.gmail.com>
> Your question isn't specific enough. What does "not compromised" mean?
Every technique for archiving records has some impact on some part of your
system. Is a 0.1% impact too
> much? A 1% impact? A 10% impact? A factor of 2 slowdown?
Sorry if my original question has not clearly conveyed my requirement.
First, let me accept that I'm not a good DBA Expert (am a beginner), however
I'm trying to learn things.
Actually, am finding out various techniques/options *itself* available for
archiving database records. Based on the techniques available, I can
see/assess on how much it could impact our application, so that I can choose
one and adopt that suits our needs. In fact your response was an eye-opener
for me to think further in detail.
> Do you need real-time archiving, a few minutes delay, or once a month
backup?
Yes, we're looking for real-time archiving. Once the records are archived,
Users in the application should able to perform search within archives also
after few minutes of time.
> Do you need a hot standby or records that can be retrieved in a few hours?
It would be helpful if you can share the techniques/options available for
hot standby also.
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: gnanam@zoniac.com, cjames@emolecules.com
Subject: Re: Database archive solutions
In-Reply-To: <00de01cdc877$15dcfcc0$4196f640$@zoniac.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