Skip site navigation (1) Skip section navigation (2)

Re: 8.2 "real-time" recovery

From: Dragos Valentin Moinescu <dragos(dot)moinescu(at)gmail(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: 8.2 "real-time" recovery
Date: 2010-08-25 14:42:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
I used rsync to create a base backup. Though I have 10 huge tables
(min 1GB each) that are modified several times a second, thus creating
a base backup hourly means I have to sync arround 10G each time (which
is pretty time consuming).

I do not want to use the standby server. This is why I am pretty happy
with stop - start + recover.

I cannot base backup anymore :(

Is there any other possibility? I cannot use slony or buccardo as I
don't control the number of databases or tables.

I think the best approach is pgpool2 but there seems to be issues with
sequences and those tables depend upon these sequences.

Thank you

On Wed, Aug 25, 2010 at 5:14 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Dragos Valentin Moinescu <dragos(dot)moinescu(at)gmail(dot)com> wrote:
>> Where can I find information about how to modify the postgresql
>> server in order to allow this in 8.2.17?
> You haven't exactly said what "this" is, but I am inferring that you
> want to bring your standby up to run read-only queries once per
> hour, and then resume replication?  If so, you could either consider
> one of the many replication solutions:
> or you could follow your current practice, but get a fresh base
> backup each time, and start the warm standby over again.  If you use
> rsync with a daemon you will probably be surprised how quickly you
> can acquire the new base backup.
> -Kevin

Best regards,
Dragos Moinescu

In response to


pgsql-admin by date

Next:From: Steve SingerDate: 2010-08-25 15:05:57
Subject: Re: HS/SR on AIX
Previous:From: Tom LaneDate: 2010-08-25 14:33:08
Subject: Re: last_autovacuum & last_autoanalyze showing NULL

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group