We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the case of accessing a very large foreign table postgres may crash.
It'd be nice to monitor memory consumption during odbcIterateForeignScan and abort gracefully any operation instead of crashing.
odbcIterateForeignScan
Note that regarding how this affects CARTO connectors, this problem should not be common since the limit on the maximum number is applied by default.
cc @ernesmb @danicarrion
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In the case of accessing a very large foreign table postgres may crash.
It'd be nice to monitor memory consumption during
odbcIterateForeignScan
and abort gracefully any operation instead of crashing.Note that regarding how this affects CARTO connectors, this problem should not be common since the limit on the maximum number is applied by default.
cc @ernesmb @danicarrion
The text was updated successfully, but these errors were encountered: