-
-
Notifications
You must be signed in to change notification settings - Fork 253
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
Stub out pgrx-internal.md #1427
Stub out pgrx-internal.md #1427
Conversation
types, and operators can in some cases cause illogical behavior from Postgres. The query executor | ||
may assume something based on the SQL definitions, causing it to interact with extensions in ways | ||
that return invalid query results or, depending on the nature of the extension, corrupt a table's | ||
active rows or index. While Postgres employs various techniques to detect such incorrect behaviors | ||
and will abort transactions and roll back if it does, and this may not be "undefined behavior" in | ||
Rust terms, it is at least as equally undesirable! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Find a way to work in the main citation for this, which is https://www.postgresql.org/docs/current/xoper-optimization.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also technically nasal demons are yet-more-powerful in the arbitrariness of the damage they can do, but anything that amounts to risking almost as much damage as DROP DATABASE production;
is uh... pretty bad!
Adds ~800 words, though it remains stubs, just in a single file.