Re: Table as argument in postgres function - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: Table as argument in postgres function
Date
Msg-id CADkLM=c+xaexd8LmfBmqMJ_M4pDQj=YFk2Xcd1hzQtOwqebk9w@mail.gmail.com
Whole thread Raw
In response to Re: Table as argument in postgres function  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Table as argument in postgres function  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers

Is there anything preventing us from having the planner resolve object names from strings?

The basic problem is fact so when you use PREPARE, EXECUTE protocol, you has not parameters in planning time.

I agree that it defeats PREPARE as it is currently implemented with PQprepare(), and it would never be meaningful to have a query plan that hasn't finalized which objects are involved.

But could it be made to work with PQexecParams(), where the parameter values are already provided?

Could we make a version of PQprepare() that takes an extra array of paramValues for object names that must be supplied at prepare-time?



 

pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: VACUUM fails to parse 0 and 1 as boolean value
Next
From: Haribabu Kommi
Date:
Subject: Re: PG 12 draft release notes