| From: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | renato(dot)oliveira(at)grant(dot)co(dot)uk, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL backup idea |
| Date: | 2010-01-20 11:53:51 |
| Message-ID: | d3ab2ec81001200353i7c59aa3bx2d05b49a1dd26baa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Jan 20, 2010 at 6:48 AM, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov
> wrote:
> Renato Oliveira wrote:
>
> > I can't implement PITR right now on our live systems, for
> > commercial reasons.
>
> What do you mean? Most of your email seems to describe techniques
> very much like PITR; why would that be OK but the existing, tested
> PITR not be OK? It's hard to know what to suggest without
> understanding the answers to those questions.
>
PITR is a one or two line update to the postgresql.conf + a base backup.
What you're talking about is trying to build your own version of this
(significantly more complex). What are the 'commercial' reasons that you
have for not using PITR, ISTM that you'd really be wasting time not using
it.
--Scott
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David F. Skoll | 2010-01-20 15:10:26 | Warm standby problems: SOLVED |
| Previous Message | Kevin Grittner | 2010-01-20 11:48:23 | Re: PostgreSQL backup idea |