Re: COPY planning - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: COPY planning
Date
Msg-id 20150922125135.GN3685@tamriel.snowman.net
Whole thread Raw
In response to Re: COPY planning  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: COPY planning
List pgsql-hackers
* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> > I noticed that COPY calls planner() (this was introduced in 85188ab88).
> > I think it should be calling pg_plan_query() instead.
>
> +1 --- AFAICS, this is the *only* place that is going directly to
> planner() without going through pg_plan_query(); other utility
> functions such as CREATE TABLE AS do the latter.
>
> As far as the patch goes, do copy.c's #include's need adjustment?
> I'm wondering if optimizer/planner.h could be removed, in particular.

BeginCopyFrom still uses expression_planner(), at least..

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Gavin Flower
Date:
Subject: Re: [COMMITTERS] pgsql: Use gender-neutral language in documentation
Next
From: Andres Freund
Date:
Subject: Re: Rework the way multixact truncations work