Date: Fri, 27 Mar 2020 10:27:52 -0700 (MST)
From: legrand legrand <legrand_legrand@hotmail.com>
To: pgsql-hackers@postgresql.org
Message-ID: <1585330072488-0.post@n3.nabble.com>
In-Reply-To: <14854.1585237484@sss.pgh.pa.us>
References: <1583789487074-0.post@n3.nabble.com>
 <6ecbaaca-5a8e-5fe6-f7e1-a893e708bd7b@oss.nttdata.com>
 <14854.1585237484@sss.pgh.pa.us>
Subject: Re: Patch: to pass query string to pg_plan_query()
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Tom Lane-2 wrote
> Fujii Masao &lt;

> masao.fujii@.nttdata

> &gt; 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.
> 
> [...]
> 
> 			regards, tom lane


Great !
Good news ;o)

Regards
PAscal


--
Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html