On Sun, Aug 9, 2009 at 6:11 AM, Simon Riggs<simon@2ndquadrant.com> wrote:
> I'm working on HS; I've said so clearly and say it again now. To my
> knowledge, no other Postgres project has committed to a timetable for
> delivery, so I'm not clear why you think one should have been given
> here, or why the absence of such a timetable implies anything. Dev tree
Well, basically because otherwise nobody except you can do anything.
In your last email you wrote:
> assistance from any and every other hacker is welcome in producing that.
What I need is some help figuring out when and how I can provide that
assistance and what I can do.
At the moment, the version of the patch that I last posted does not
apply due to a conflict in sinval.h, I believe due to conflicts
introduced by Fujii Masao's signal multiplexing patch. I haven't had
time to look at that in any detail yet, but I'd like to do do so soon.There are some other things that look like easy
cleanupsthat I think
I could knock out as well; see my original email on this thread. Of
course, your input on those items would be invaluable. Of course, if
you've already done some of this work, that would be great, but then
it seems like you ought to have let us know that you were doing it
before you did it, and posted the updated patch to -hackers
afterwards, just as you asked me to do.
Working disconnected from everyone else until September 15th (or
November 15th) and then posting the patch will make it very, very
difficult for anyone else to do anything useful. When I was working
the explain patches, I posted them regularly to -hackers, and
published a git repository on git.postgresql.org, which meant that
anyone could follow along at home if they wished. Since Hot Standby
is more interesting before breakfast than machine-readable explain
output is all day, the same approach seems desirable here. At the
very least, I think you should post your progress weekly so that we
can read, review, comment, propose changes...
...Robert
