| From: | Yash Jadhav <yash(dot)jadhav8008(at)gmail(dot)com> |
|---|---|
| To: | Koshino Taiki <koshino(at)sraoss(dot)co(dot)jp> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> |
| Subject: | Re: Proposal: Include CHECK constraint expression in violation error DETAIL |
| Date: | 2026-10-29 19:23:20 |
| Message-ID: | CAGsfjr5TmF5LFt=ofrm5gDS-6-AamQqa12_eafHyL-r16R9UTw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I went through the patch and have a few thoughts on the security question.
> Is there a reason why the expression is not included in the error detail?
> (For example, having such information appear in logs could pose a
> security risk.)
For clients: any role can read CHECK expressions from, including for
tables it has no privileges on, so printing the expression doesn't
seem to expose anything new.
For the server log: an error entry already contains the table, column
and constraint names, so expression looks less sensitive compared to
them.
Anything I should improve on?
Regards,
Yash
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2026-10-29 20:33:29 | Re: WAL record CRC calculated incorrectly because of underlying buffer modification |
| Previous Message | Jim Jones | 2026-10-29 19:15:52 | Re: CREATE TABLE .. LIKE copies comments to an unrelated table |