Responses inline below
Thanks,
reid
-Original Message-
From: Tom Lane
Sent: Monday, April 19, 2021 9:54 AM
To: Reid Thompson
Cc: pgsql-general@lists.postgresql.org
Subject: Re: could not read from hash-join temporary file: SUCCESS && DB goes
into recovery mode
Reid Thompson
@lists.postgresql.org
Subject: Re: could not read from hash-join temporary file: SUCCESS && DB goes
into recovery mode
[EXTERNAL SOURCE]
On 2021-Apr-19, Reid Thompson wrote:
> Thanks - I found that, which seems to fix the error handling right? Or
> does it actually correct the cause o
On 2021-Apr-19, Reid Thompson wrote:
> Thanks - I found that, which seems to fix the error handling right? Or
> does it actually correct the cause of the segfault also?
Uh, what segfault? You didn't mention one. Yes, it fixes the error
handling, so when the system runs out of disk space, that's
issue until then?
-Original Message-
From: Alvaro Herrera
Sent: Monday, April 19, 2021 10:09 AM
To: Reid Thompson
Cc: pgsql-general@lists.postgresql.org
Subject: Re: could not read from hash-join temporary file: SUCCESS && DB goes
into recovery mode
[EXTERNAL SOURCE]
On 202
On 2021-Apr-19, Reid Thompson wrote:
> Hi I'm looking for some guidance related to the subject line issue.
> PostgreSQL 11.8 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623
> (Red Hat 4.8.5-39), 64-bit
> 128GB RAM
> pgsql_tmp is on a FS with 2+TB free
This bug report looks familiar.
Reid Thompson writes:
> Hi I'm looking for some guidance related to the subject line issue.
Is this repeatable? If so you've found a bug, I think.
> 1. That the error message has been updated ( i.e. SUCCESS is not the
> proper value)
Yeah, what this really indicates is an incomplete read (
Hi I'm looking for some guidance related to the subject line issue.
PostgreSQL 11.8 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623
(Red Hat 4.8.5-39), 64-bit
128GB RAM
pgsql_tmp is on a FS with 2+TB free
Information that I've been able to find on the web indicates
1. That the er
