diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-01-26 16:37:12 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-01-26 16:37:12 -0500 |
commit | d5a83d79c9f9b660a6a5a77afafe146d3c8c6f46 (patch) | |
tree | e0c3626c5bd5369cf1433a42a1db1d9df9dd53ba /src/backend/access/gist/gist.c | |
parent | 7292fd8f1c781278021407276474d9188845113d (diff) | |
download | postgresql-d5a83d79c9f9b660a6a5a77afafe146d3c8c6f46.tar.gz |
Rethink recently-added SPI interfaces.
SPI_execute_with_receiver and SPI_cursor_parse_open_with_paramlist are
new in v14 (cf. commit 2f48ede08). Before they can get out the door,
let's change their APIs to follow the practice recently established by
SPI_prepare_extended etc: shove all optional arguments into a struct
that callers are supposed to pre-zero. The hope is to allow future
addition of more options without either API breakage or a continuing
proliferation of new SPI entry points. With that in mind, choose
slightly more generic names for them: SPI_execute_extended and
SPI_cursor_parse_open respectively.
Discussion: https://postgr.es/m/CAFj8pRCLPdDAETvR7Po7gC5y_ibkn_-bOzbeJb39WHms01194Q@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions