Re: Hot standby, RestoreBkpBlocks and cleanup locks

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hot standby, RestoreBkpBlocks and cleanup locks
Date: 2009-01-20 19:56:10
Message-ID: 49762C5A.5080600@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
> I did want you to commit those changes, but that was 8 days ago and much
> has changed since then. Now, I'm slightly worried that this may be a
> retrograde step. The last 3 days I've been refactoring the code to
> account for other requirements, as I have been discussing, and some of
> these things have now changed. Though the general pattern of your
> suggested refactoring remains the same.

I figured there's possibly some further changes, but the general idea to
move the responsibility of restoring backup blocks to the redo function
should remain the same.

> Can we plan a move to GIT? We can both work on things at the same time
> and my changes can be more visible. There will be some initial pain...

Sure, just go ahead and publish a repository. Or would you like me to
apply the patches and publish a repository you can clone from? Perhaps
that would be easier since I'm already familiar with GIT.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-01-20 20:40:37 Re: Visibility map and freezing
Previous Message Heikki Linnakangas 2009-01-20 19:51:01 Re: Visibility map and freezing