Re: Refactor parse analysis of EXECUTE command - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Refactor parse analysis of EXECUTE command
Date
Msg-id bd4f429b-e7bd-93f4-a4b8-4368c5afa8a3@2ndquadrant.com
Whole thread Raw
In response to Re: Refactor parse analysis of EXECUTE command  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Refactor parse analysis of EXECUTE command  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
After digesting the discussion, let's reshuffle this a bit.

I have committed the change that adds the error location in one place. 
That worked independently.

Attached is a new patch that refactors things a bit to pass the 
ParseState into functions such as PrepareQuery() and ExecuteQuery() 
instead of passing the query string and query environment as a separate 
arguments.  We had already done that for most utility commands; there 
were just some left that happened to be involved in the current thread's 
discussion anyway.

That's a nice cosmetic improvement in any case, but I think that it 
would also help with the issue of passing parameters into some utility 
commands later on.  I will look into that some other time.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Update minimum SSL version
Next
From: vignesh C
Date:
Subject: Re: dropdb --force