A problem about LEAKPROOF of postgresql - Mailing list pgsql-bugs

From David G. Johnston
Subject A problem about LEAKPROOF of postgresql
Date
Msg-id CAKFQuwY5wQZkf-U_YG5RD_o=Zsf-rkLSabHBqKpnLc090QfUXQ@mail.gmail.com
Whole thread Raw
In response to A problem about LEAKPROOF of postgresql  ("qiumingcheng" <qiumingcheng@aliyun.com>)
List pgsql-bugs
On Wednesday, September 7, 2022, qiumingcheng <qiumingcheng@aliyun.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.


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.

pgsql-bugs by date:

Previous
From: "qiumingcheng"
Date:
Subject: A problem about LEAKPROOF of postgresql
Next
From: "James Pang (chaolpan)"
Date:
Subject: huge memory of Postgresql backend process