Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Postgres.Call #11

Open
jwp opened this issue Jan 28, 2010 · 1 comment
Open

Implement Postgres.Call #11

jwp opened this issue Jan 28, 2010 · 1 comment
Labels

Comments

@jwp
Copy link
Contributor

jwp commented Jan 28, 2010

Currently, direct function calls cannot leverage SRFs or functions that keep state.

An explicit Call object to manage that state is necessary. This is, essentially, objectified fcinfo.

@jwp
Copy link
Contributor Author

jwp commented Jan 29, 2010

Postgres.Call needs to have some intelligence in order to distinguish between SRFs and regular functions; this also has some impact on the supported interfaces:

SRFs will only support next
Non-SRFs will support call()

VPC-SRFs will likely be the supported mode, and each call will need it's own MemoryContext.

Also, consider an optimization for SRFs that return a Call() like Postgres.Cursor() returns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant