From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, "heikki(dot)linnakangas" <heikki(dot)linnakangas(at)iki(dot)fi> |
Subject: | Re: Using pg_rewind for differential backup |
Date: | 2014-12-02 17:32:46 |
Message-ID: | CA+TgmoZkRJPtXJg-fVEVC7w7cft4gY5T9nFp93dKnVL6bC9H=w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 28, 2014 at 2:49 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> It also would be quite straightforward to write a separate tool to do just
> that. Would be better than conflating pg_rewind with this. You could use
> pg_rewind as the basis for it - it's under the same license as PostgreSQL.
If we had such a tool in core, would that completely solve the
differential backup problem, or would more be needed?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-12-02 17:37:46 | Re: Fillfactor for GIN indexes |
Previous Message | Robert Haas | 2014-12-02 17:26:33 | Re: Testing DDL deparsing support |