Movatterモバイル変換


[0]ホーム

URL:



Facebook
Postgres Pro
Facebook
Downloads
SPI_execute_plan_extended
Prev Up45.1. Interface FunctionsHome Next

SPI_execute_plan_extended

SPI_execute_plan_extended — execute a statement prepared bySPI_prepare

Synopsis

int SPI_execute_plan_extended(SPIPlanPtrplan,                              const SPIExecuteOptions *options)

Description

SPI_execute_plan_extended executes a statement prepared bySPI_prepare or one of its siblings. This function is equivalent toSPI_execute_plan, except that information about the parameter values to be passed to the query is presented differently, and additional execution-controlling options can be passed.

Query parameter values are represented by aParamListInfo struct, which is convenient for passing down values that are already available in that format. Dynamic parameter sets can also be used, via hook functions specified inParamListInfo.

Also, instead of always accumulating the result tuples into aSPI_tuptable structure, tuples can be passed to a caller-suppliedDestReceiver object as they are generated by the executor. This is particularly helpful for queries that might generate many tuples, since the data can be processed on-the-fly instead of being accumulated in memory.

Arguments

SPIPlanPtrplan

prepared statement (returned bySPI_prepare)

const SPIExecuteOptions *options

struct containing optional arguments

Callers should always zero out the entireoptions struct, then fill whichever fields they want to set. This ensures forward compatibility of code, since any fields that are added to the struct in future will be defined to behave backwards-compatibly if they are zero. The currently availableoptions fields are:

ParamListInfoparams

data structure containing query parameter types and values; NULL if none

boolread_only

true for read-only execution

boolallow_nonatomic

true allows non-atomic execution of CALL and DO statements (but this field is ignored unless theSPI_OPT_NONATOMIC flag was passed toSPI_connect_ext)

boolmust_return_tuples

iftrue, raise error if the query is not of a kind that returns tuples (this does not forbid the case where it happens to return zero tuples)

uint64tcount

maximum number of rows to return, or0 for no limit

DestReceiver *dest

DestReceiver object that will receive any tuples emitted by the query; if NULL, result tuples are accumulated into aSPI_tuptable structure, as inSPI_execute_plan

ResourceOwnerowner

The resource owner that will hold a reference count on the plan while it is executed. If NULL, CurrentResourceOwner is used. Ignored for non-saved plans, as SPI does not acquire reference counts on those.

Return Value

The return value is the same as forSPI_execute_plan.

Whenoptions->dest is NULL,SPI_processed andSPI_tuptable are set as inSPI_execute_plan. Whenoptions->dest is not NULL,SPI_processed is set to zero andSPI_tuptable is set to NULL. If a tuple count is required, the caller'sDestReceiver object must calculate it.


Prev Up Next
SPI_execute_plan Home SPI_execute_plan_with_paramlist
pdfepub
Go to PostgreSQL 17
By continuing to browse this website, you agree to the use of cookies. Go toPrivacy Policy.

[8]ページ先頭

©2009-2025 Movatter.jp