From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <tmunro(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Prefetch data referenced by the WAL, take II. |
Date: | 2022-04-07 13:53:43 |
Message-ID: | 3279390.1649339623@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 4/7/22 04:36, Andres Freund wrote:
>> Or maybe it's the scripts that are screwed up? Because I don't see any error
>> checking in headerscheck/cpluspluscheck. And indeed, locally they show the
>> errors, but exit with 0.
> Yeah, you can't rely on the exit status, if they produce output that
> should be regarded as a failure (that's what crake does).
Yeah, those scripts were only intended to be run by hand. If someone
feels like upgrading them to also produce a useful exit status,
I'm for it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2022-04-07 14:04:20 | Re: API stability [was: pgsql: Fix possible recovery trouble if TRUNCATE overlaps a checkpoint.] |
Previous Message | Andrew Dunstan | 2022-04-07 12:18:05 | Re: pgsql: Prefetch data referenced by the WAL, take II. |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2022-04-07 14:01:09 | Re: Preventing indirection for IndexPageGetOpaque for known-size page special areas |
Previous Message | Tom Lane | 2022-04-07 13:49:01 | Re: Remove error message hints mentioning configure options |