| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: aggregate crash |
| Date: | 2020-01-14 22:01:01 |
| Message-ID: | 9344.1579039261@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2019-Dec-27, Teodor Sigaev wrote:
>> Found crash on production instance, assert-enabled build crashes in pfree()
>> call, with default config. v11, v12 and head are affected, but, seems, you
>> need to be a bit lucky.
> Is this bug being considered for the next set of minors?
I think Andres last touched that code, so I was sort of expecting
him to have an opinion on this. But I agree that not checking null-ness
explicitly is kind of unsafe. We've never before had any expectation
that the Datum value of a null is anything in particular.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2020-01-14 22:03:33 | Re: Unicode escapes with any backend encoding |
| Previous Message | Daniel Gustafsson | 2020-01-14 22:01:00 | Re: Setting min/max TLS protocol in clientside libpq |