| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "qiumingcheng" <qiumingcheng(at)aliyun(dot)com> |
| Cc: | "Laurenz Albe" <laurenz(dot)albe(at)cybertec(dot)at>, "Julien Rouhaud" <rjuju123(at)gmail(dot)com>, "pgsql-general" <pgsql-general(at)lists(dot)postgresql(dot)org>, "yuexingzhi" <yuexingzhi(at)hotmail(dot)com> |
| Subject: | Re: 回复：回复：回复：A question about leakproof |
| Date: | 2022-10-17 14:07:18 |
| Message-ID: | 2163397.1666015638@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"qiumingcheng" <qiumingcheng(at)aliyun(dot)com> writes:
> 2. What's the reason about the function timestamp_gt_timestampz may cause data leakage? Can you explain how it causes data leakage?
It's capable of throwing an error (see
timestamp2timestamptz_opt_overflow). Now, maybe that's unreachable, or
maybe we could rerrange things to remove it. But there's still enough
code underneath the timezone conversion requirement that I'd be very
hesitant to apply a leakproof marking. In short: it might be leakproof
in practice, but we don't wish to offer a guarantee.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2022-10-17 14:07:33 | Re: 回复：回复：回复：A question about leakproof |
| Previous Message | jacktby | 2022-10-17 14:07:02 | could not find shared library for Python |