|From:||Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>|
|To:||Chapman Flack <chap(at)anastigmatix(dot)net>|
|Subject:||Re: Re: PROPOSAL: make PostgreSQL sanitizers-friendly (and prevent information disclosure)|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> Well, the documentation already says to avoid it:
> Another important point is to avoid leaving any uninitialized
> bits within data type values; for example, take care to zero out
> any alignment padding bytes that might be present in structs.
> so I don't think what you're suggesting would be controversial
> at all; it looks like what you've done is found a(t least one)
> bug where the documented practice wasn't followed, and it's good
> to find any such places.
Well in this case here is a patch that fixes "use of uninitialized
value" reports by MemorySanitizer I managed to catch so far.
|Next Message||Ashutosh Bapat||2016-03-21 14:32:00||Re: Postgres_fdw join pushdown - getting server crash in left outer join of three table|
|Previous Message||Petr Jelinek||2016-03-21 14:14:43||Re: Proposal: Generic WAL logical messages|