| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net>, <pgsql-general(at)postgresql(dot)org>, <ramkumar(dot)yelai(at)siemens(dot)com> |
| Subject: | Re: Pgbasebackup help |
| Date: | 2015-12-02 23:25:37 |
| Message-ID: | 565F7DF1.7070007@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/2/15 1:56 PM, David Steele wrote:
>> >Also, I don’t want enable archive_mode = on as it needs to maintain
>> >archives files.
> As it turns out, archiving would be the solution to your problem. If
> you were archiving you could restore a*previous* backup and then replay
> WAL to exactly T3. There might be some jitter from clock differences
> but it should have the desired effect.
And in this case previous could be a PG backup taken immediately before
the backup of the private DBMS.
I don't remember off-hand if pg_basebackup has an option for delaying
the pg_stop_backup() call, but if it does then I think the simplest
thing is to just delay that until after your private DBMS backup is
complete.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-12-03 00:04:13 | Re: json indexing and data types |
| Previous Message | Jim Nasby | 2015-12-02 23:20:40 | Re: XID wraparound with huge pg_largeobject |