From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
cc: legrand legrand <legrand_legrand@hotmail.com>,
        pgsql-hackers@postgresql.org
Subject: Re: Patch: to pass query string to pg_plan_query()
In-reply-to: <6ecbaaca-5a8e-5fe6-f7e1-a893e708bd7b@oss.nttdata.com>
References: <1583789487074-0.post@n3.nabble.com>
 <6ecbaaca-5a8e-5fe6-f7e1-a893e708bd7b@oss.nttdata.com>
Comments: In-reply-to Fujii Masao <masao.fujii@oss.nttdata.com>
	message dated "Thu, 26 Mar 2020 22:54:35 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <14853.1585237484.1@sss.pgh.pa.us>
Date: Thu, 26 Mar 2020 11:44:44 -0400
Message-ID: <14854.1585237484@sss.pgh.pa.us>
Precedence: bulk

Fujii Masao <masao.fujii@oss.nttdata.com> writes:
> Does anyone object to this patch? I'm thinking to commit it separetely
> at first before committing the planning_counter_in_pg_stat_statements
> patch.

I took a quick look through v9-0001-Pass-query-string-to-the-planner.patch
and it's fine by me.  It also matches up with something I've wanted to
do for awhile, which is to make the query string available during
planning and execution so that we can produce error cursors for
run-time errors, when relevant.

(It's a little weird that the patch doesn't make standard_planner
actually *do* anything with the string, like say save it into
the PlannerInfo struct.  But that can come later I guess.)

Note that I wouldn't want to bet that all of these call sites always have
non-null query strings to pass; but probably most of the time they will.

			regards, tom lane