| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BufFileRead() error signalling |
| Date: | 2020-05-27 16:29:00 |
| Message-ID: | CA+TgmoZEmoMLfSmtSOqYwadAGsejzZkT5MMgpRxE1a=uhoPEoQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 27, 2020 at 12:16 PM Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> I do have evidence of postgres crashes because of a problem that could
> be explained by this bug, so I +1 backpatching this to all supported
> branches.
>
> (The problem I saw is a hash-join spilling data to temp tablespace,
> which fills up but somehow goes undetected, then when reading the data
> back it causes heap_fill_tuple to crash.)
FWIW, that seems like a plenty good enough reason for back-patching to me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-05-27 16:35:12 | Re: New 'pg' consolidated metacommand patch |
| Previous Message | Alvaro Herrera | 2020-05-27 16:16:07 | Re: BufFileRead() error signalling |