Re: clearing opfuncid vs. parallel query - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: clearing opfuncid vs. parallel query
Date
Msg-id CAPpHfdsscC+OyJiOaoz+rMUS0w26YgMNwfXp1QU39+oUjyn6dw@mail.gmail.com
Whole thread Raw
In response to Re: clearing opfuncid vs. parallel query  (YUriy Zhuravlev <u.zhuravlev@postgrespro.ru>)
Responses Re: clearing opfuncid vs. parallel query  (YUriy Zhuravlev <u.zhuravlev@postgrespro.ru>)
List pgsql-hackers
On Fri, Oct 23, 2015 at 12:31 PM, YUriy Zhuravlev <u.zhuravlev@postgrespro.ru> wrote:
On Thursday 22 October 2015 09:26:46 David Fetter wrote:
> On Thu, Oct 22, 2015 at 07:15:35PM +0300, YUriy Zhuravlev wrote:
> > Hello.
> > Currently using nodeToString and stringToNode you can not pass a
> > full plan. In this regard, what is the plan to fix it? Or in the
> > under task parallel query does not have such a problem?
> >
> > > This turns out not to be straightforward to code, because we don't
> > > have a generic plan tree walker,
> >
> > I have an inner development. I am using python analyzing header
> > files and generates a universal walker (parser, paths ,executer and
> > etc trees), as well as the serializer and deserializer to jsonb.
> > Maybe I should publish this code?
>
> Please do.
Tom Lane and Robert Haas are very unhappy with a python. Is there any reason?

Requirement of python with pycparser as build dependency is a serious cataclysm. For instance, how many buildfarms will survive it?
This is why Tom and Robert are looking for ways to evade it.

------

Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company 

pgsql-hackers by date:

Previous
From: YUriy Zhuravlev
Date:
Subject: Re: clearing opfuncid vs. parallel query
Next
From: Etsuro Fujita
Date:
Subject: Re: ATT_FOREIGN_TABLE and ATWrongRelkindError()