postgres-xc-developers Mailing List for Postgres-XC

Hi Micheal,
Are we not suppose to just merge the changes from the 92 stable branch?

Thanks,
Ahsan

On Thu, Jul 26, 2012 at 10:10 AM, Michael Paquier <mic...@gm...
> wrote:

> Hi all,
>
> I am going to work on merging Postgres 9.2 code with XC.
> The goal is to plug in XC code up to the intersection of 9.2 stable branch
> and postgres master branch. By respecting this, we will then be able to
> plug in 9.2 stable branch for our future stable releases and postgresql
> master branch in the future.
>
> I am just beginning to have a look at that, so I still cannot really
> estimate the effort necessary to do that yet. However here is the commit I
> will merge up to:
> commit 80edfd76591fdb9beec061de3c05ef4e9d96ce56
> Author: Tom Lane <tg...@ss...>
> Date:   Wed Jun 13 19:43:35 2012 -0400
>
>     Revisit error message details for JSON input parsing.
>
>     Instead of identifying error locations only by line number (which could
>     be entirely unhelpful with long input lines), provide a fragment of the
>     input text too, placing this info in a new CONTEXT entry.  Make the
>     error detail messages conform more closely to style guidelines, fix
>     failure to expose some of them for translation, ensure compiler can
>     check formats against supplied parameters.
> This commit can be found with this command: git merge-base postgres/master
> postgres/REL9_2_STABLE.
>
> Once I got something compilable, I will commit a version of the merge in a
> new branch of my github repository of XC =>
> https://github.com/michaelpq/pgxc.
> And once I got some stabilization work done, I will simply merge this
> branch with the existing XC master and commit everything into XC master.
> I might begin the merge from commit
> d03ea805cef9375bee9b751e65d698c07c138bf5 on XC master branch.
> There will be for sure some other commits while I do the merge, but I will
> just include them once I got a faily stable version.
>
> Comments are welcome.
> --
> Michael Paquier
> http://michael.otacoo.com
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>


-- 
Ahsan Hadi
Snr Director Product Development
EnterpriseDB Corporation
The Enterprise Postgres Company

Phone: +92-51-8358874
Mobile: +92-333-5162114

Website: www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb

This e-mail message (and any attachment) is intended for the use of the
individual or entity to whom it is addressed. This message contains
information from EnterpriseDB Corporation that may be privileged,
confidential, or exempt from disclosure under applicable law. If you are
not the intended recipient or authorized to receive this for the intended
recipient, any use, dissemination, distribution, retention, archiving, or
copying of this communication is strictly prohibited. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete this message.

Hi all,

I am going to work on merging Postgres 9.2 code with XC.
The goal is to plug in XC code up to the intersection of 9.2 stable branch
and postgres master branch. By respecting this, we will then be able to
plug in 9.2 stable branch for our future stable releases and postgresql
master branch in the future.

I am just beginning to have a look at that, so I still cannot really
estimate the effort necessary to do that yet. However here is the commit I
will merge up to:
commit 80edfd76591fdb9beec061de3c05ef4e9d96ce56
Author: Tom Lane <tg...@ss...>
Date:   Wed Jun 13 19:43:35 2012 -0400

    Revisit error message details for JSON input parsing.

    Instead of identifying error locations only by line number (which could
    be entirely unhelpful with long input lines), provide a fragment of the
    input text too, placing this info in a new CONTEXT entry.  Make the
    error detail messages conform more closely to style guidelines, fix
    failure to expose some of them for translation, ensure compiler can
    check formats against supplied parameters.
This commit can be found with this command: git merge-base postgres/master
postgres/REL9_2_STABLE.

Once I got something compilable, I will commit a version of the merge in a
new branch of my github repository of XC =>
https://github.com/michaelpq/pgxc.
And once I got some stabilization work done, I will simply merge this
branch with the existing XC master and commit everything into XC master.
I might begin the merge from commit
d03ea805cef9375bee9b751e65d698c07c138bf5 on XC master branch.
There will be for sure some other commits while I do the merge, but I will
just include them once I got a faily stable version.

Comments are welcome.
-- 
Michael Paquier
http://michael.otacoo.com