From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it> |
Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [RFC] Incremental backup v2: add backup profile to base backup |
Date: | 2014-10-03 18:19:20 |
Message-ID: | 20141003181920.GH14522@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Oct 3, 2014 at 06:08:47PM +0200, Marco Nenciarini wrote:
> >> Any comment will be appreciated. In particular I'd appreciate comments
> >> on correctness of relnode files detection and LSN extraction code.
> >
> > I didn't look at it in detail, but one future problem comes to mind:
> > Once you implement the server-side code that only sends a file if its
> > LSN is higher than the cutoff point that the client gave, you'll have to
> > scan the whole file first, to see if there are any blocks with a higher
> > LSN. At least until you find the first such block. So with a file-level
> > implementation of this sort, you'll have to scan all files twice, in the
> > worst case.
> >
>
> It's true. To solve this you have to keep a central maxLSN directory,
> but I think it introduces more issues than it solves.
The central issue Heikki is pointing out is whether we should implement
a file-based system if we already know that a block-based system will be
superior in every way. I agree with that and agree that implementing
just file-based isn't worth it as we would have to support it forever.
So, in summary, if you target just a file-based system, be prepared that
it might be rejected.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-10-03 18:21:12 | Re: replicating DROP commands across servers |
Previous Message | Bruce Momjian | 2014-10-03 18:10:46 | Re: Fixed xloginsert_locks for 9.4 |