extension: disable some optimizations for extension function

[lcwangchao]

What problem does this PR solve?

Issue Number: close #51925

Problem Summary:

If an extension function has some side-effect, it may be optimized by mistake. For example, if a function myfunc returns a random int, select id, myfunc() from t may produce same values for myfunc because it have been fold to a constant.

Another problem is that if an extension function requires some privilege, it will only be checked when building it. That causes some problems when the plan cache is enabled because the privilege will not be check again when evaluating a function and a user's privileges may be revoked.

We should avoid these unnecessary optimizations.

What changed and how does it work?

Disable some optimizations for extension functions.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @lcwangchao. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[codecov]

Codecov Report

Merging #51926 (31ff7ce) into master (161a223) will decrease coverage by 16.0393%.
Report is 1 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #51926         +/-   ##
=================================================
- Coverage   70.6700%   54.6307%   -16.0393%     
=================================================
  Files          1477       1588        +111     
  Lines        438718     608384     +169666     
=================================================
+ Hits         310042     332365      +22323     
- Misses       109176     252925     +143749     
- Partials      19500      23094       +3594     

Flag	Coverage Δ
integration	36.5462% <0.0000%> (?)
unit	70.4625% <100.0000%> (+0.0019%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	51.4053% <ø> (+5.6008%)	⬆️

[YangKeao]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-03-20 05:41:21.927282913 +0000 UTC m=+1441708.949529301: ☑️ agreed by YangKeao.
• 2024-03-20 06:43:56.607131809 +0000 UTC m=+1445463.629378196: ☑️ agreed by qw4990.

[windtalker]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qw4990, windtalker, YangKeao

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [YangKeao,qw4990,windtalker]
• pkg/expression/OWNERS [windtalker]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #51944.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #51946.