| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | qiumingcheng <qiumingcheng(at)aliyun(dot)com> |
| Cc: | pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>, qiumingcheng <qiumingcheng(at)huawei(dot)com> |
| Subject: | A problem about LEAKPROOF of postgresql |
| Date: | 2022-09-08 06:04:45 |
| Message-ID: | CAKFQuwY5wQZkf-U_YG5RD_o=Zsf-rkLSabHBqKpnLc090QfUXQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wednesday, September 7, 2022, qiumingcheng <qiumingcheng(at)aliyun(dot)com>
wrote:
>
> Please help to answer: in the optimizer stage, if I remove the code in
> the red box below, what will be the problem。
>
>
Please do not direct general inquiries to the bug reporting mailing list.
We have the -general mailing list for that.
Please consult the documentation for leakproof.
https://www.postgresql.org/docs/current/sql-createfunction.html
Removing said code will constitute a data leak vector as the subsequent
debug message says. The planner doesn’t get to apply other filters at this
step so the data being fed to the function is assumed to contain data the
user is not allowed to see and thus must not be leaked from the system.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Pang (chaolpan) | 2022-09-08 06:10:28 | huge memory of Postgresql backend process |
| Previous Message | qiumingcheng | 2022-09-08 05:12:03 | A problem about LEAKPROOF of postgresql |