Re: [Postgres-xc-developers] Fix for compile duo to Bison 3.0 update

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

Hmm... As Michael suggested, applying this patch only locally to XC will
make it difficult to keep XC code synchronized with vanilla PG.    We
should wait until this patch is included in vanilla PG.

Regards;
---
Koichi Suzuki


2013/8/19 Michael Paquier <mic...@gm...>

> On Tue, Aug 13, 2013 at 5:28 AM, Jure Kobal <j....@gm...> wrote:
> > Since Bison 3.0 they stopped support for YYPARSE_PARAM, which is used in
> > contrib/cube and contrib/seg. More can be read at:
> > http://www.postgresql.org/message-id/736...@ss...
> >
> > There is a patch for PostgreSQL which fixes this but doesn't apply clean
> on
> > Postgres-XC 1.0.3 without some minor changes.
> >
> > Attached is the patch for 1.0.3. Tested with bison 3.0 and 2.7.1. Both
> compile
> > without errors.
> Yes, this is definitely something to be aware of, but -1 for the patch
> as this fix has been committed in the Postgres code tree, and XC
> should directly pick it up from there by merging all its active
> branches with the latest commits of postgres.
> --
> Michael
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>