Re: [Postgres-xc-developers] Status of the current master

[Koichi S. <koi...@gm...>]

Yes, this is the mistake we've made in this merge.    The merge took
very long due to internal API change in the planner.    I planned to
make master branch as stable as possible and the merge can be seen as
a single commit.   This made all the process and communication almost
invisible.

I'm going to do the following after I stabilize the current master:

1) Merge with PG 9.3,
2) Merge current master with the latest PG master.

They may take a bit long and I'm planning to make intermediate status
visible to public so that I can have many more help.

Ideas or thoughts?
---
Koichi Suzuki


2014-01-31 Michael Paquier <mic...@gm...>:
> On Fri, Jan 31, 2014 at 10:29 AM, Koichi Suzuki <koi...@gm...> wrote:
>> The master was updated with master_pg93_merge and it was found that we
>> still need some more work to stabilize it, some conflict and errors
>> found in DBT-1 benchmark run.
>>
>> Please allow a bit more for stabilization.
> That's a development branch. It is made to be unstable :). You could
> actually have done the merge of 9.3 directly on master IMO without
> using the intermediate branch master_pg93_merge.
> --
> Michael