Re: Schedule for 9.5alpha1

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
> Sent: Friday, June 26, 2015 12:00 AM
> To: pgsql-hackers(at)postgreSQL(dot)org
> Subject: [HACKERS] Schedule for 9.5alpha1
>
> There was agreement at the PGCon dev meeting that we should put out a
> 9.5alpha1 release as soon as possible, to encourage wider testing
> (and that it should be called an "alpha", because people aren't convinced
> it's up to beta quality yet). After a little back and forth, that release
> has been set for next week, ie we'll wrap Monday June 29 for public
> announcement Thursday July 2.
>
> If there are any open 9.5 issues you can fix before Monday, please do.
>
I have a serious open item reported 1.5 month ago then reminded
several times has not been fixed up yet.

9A28C8860F777E439AA12E8AEA7694F8010F3EA6(at)BPXM15GP(dot)gisp(dot)nec(dot)co(dot)jp

Patch is less than 100 lines, entirely designed according to Tom's suggestion.

The problem is, commit 1a8a4e5cde2b7755e11bde2ea7897bd650622d3e reverted
create_plan_recurse() to static function, thus, extension lost way to
transform Path node to Plan node if it wants to takes underlying child
nodes, like SeqScan, HashJoin and so on.

Tom's suggestion is to add a list of Path nodes on CustomPath structure,
to be transformed by createplan.c, instead of public create_plan_recurse().

It is nearly obvious problem, and bugfix patch already exists.

Thanks,
--
NEC Business Creation Division / PG-Strom Project
KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>